Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add References section. #4276

Merged
merged 10 commits into from
Feb 23, 2023

Conversation

osg-grafana
Copy link
Contributor

No description provided.

@osg-grafana osg-grafana linked an issue Feb 22, 2023 that may be closed by this pull request
@osg-grafana osg-grafana self-assigned this Feb 22, 2023
@osg-grafana osg-grafana marked this pull request as ready for review February 22, 2023 18:01
@osg-grafana osg-grafana requested review from a team as code owners February 22, 2023 18:01
@osg-grafana osg-grafana marked this pull request as draft February 22, 2023 18:02
…ronment-with-helm/configuration-with-helm.md
@@ -0,0 +1,20 @@
---
title: "Grafana Mimir references"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@knylander-grafana, I could use your input about how we can standardize the _index.md file for references across the DB docs. Have thoughts on this?

Copy link
Contributor

@knylander-grafana knylander-grafana Feb 22, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider these topics:

  • Introduction - section purpose with high-level description, philosophy of how things are organized (if applicable)
  • Info of any major groupings of references, like developer content, configuration, architecture, etc.

After that, have your list of {{<section>}}

@osg-grafana osg-grafana marked this pull request as ready for review February 23, 2023 09:35
@osg-grafana
Copy link
Contributor Author

@pracucci, added you for visibility.

Copy link
Contributor

@flxbk flxbk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@osg-grafana osg-grafana removed the request for review from pracucci February 23, 2023 10:28
@pracucci pracucci self-requested a review February 23, 2023 14:35
Copy link
Collaborator

@pracucci pracucci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (modulo one comment). Thanks!

@@ -10,7 +10,7 @@ aliases:

# Manage the configuration of Grafana Mimir with Helm

The `mimir-distributed` Helm chart provides interfaces to set Grafana Mimir [configuration parameters](/docs/mimir/v2.5.x/operators-guide/configure/reference-configuration-parameters/) and customize how Grafana Mimir is deployed on a Kubernetes cluster. This document describes the configuration parameters.
The `mimir-distributed` Helm chart provides interfaces to set Grafana Mimir [configuration parameters](/docs/mimir/v2.5.x/operators-guide/configure/references-configuration-parameters/) and customize how Grafana Mimir is deployed on a Kubernetes cluster. This document describes the configuration parameters.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't be like this?

Suggested change
The `mimir-distributed` Helm chart provides interfaces to set Grafana Mimir [configuration parameters](/docs/mimir/v2.5.x/operators-guide/configure/references-configuration-parameters/) and customize how Grafana Mimir is deployed on a Kubernetes cluster. This document describes the configuration parameters.
The `mimir-distributed` Helm chart provides interfaces to set Grafana Mimir [configuration parameters](/docs/mimir/v2.5.x/operators-guide/configure/references/configuration-parameters/) and customize how Grafana Mimir is deployed on a Kubernetes cluster. This document describes the configuration parameters.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think so because it is a static link to a specific release. @krajorama, this is what we decided, right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we've decided to link the correct Mimir/GEM documentation from the Helm chart docs. Which means the version that the chart actually contains. Hopefully this will be done with some version variable that we can set in one place sometime in the not so distant future.
Given this, the v2.5.x documentation is in the right place already, no need to change in this PR I think.

@osg-grafana osg-grafana merged commit 171db62 into main Feb 23, 2023
@osg-grafana osg-grafana deleted the 4275-docs-create-a-top-level-references-section branch February 23, 2023 18:15
krajorama added a commit that referenced this pull request Mar 14, 2023
Fix configuration parameter reference link. Ref: #4276
Update link to HA dedup setup with Consul to be a relref, since it
was moved into the Helm docs. Ref: #4338

Signed-off-by: György Krajcsovits <[email protected]>
krajorama added a commit that referenced this pull request Mar 14, 2023
Fix configuration parameter reference link. Ref: #4276
Update link to HA dedup setup with Consul to be a relref, since it
was moved into the Helm docs. Ref: #4338

Signed-off-by: György Krajcsovits <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docs: Create a top-level references section
5 participants