chore: Add relabeling rules flags #3462
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
simonswine
added
type/docs
simonswine
changed the title
|
This PR must be merged before a backport PR will be created. |
1 similar comment
|
This PR must be merged before a backport PR will be created. |
simonswine
commented
Aug 1, 2024
| @@ -1843,6 +1843,8 @@ The `limits` block configures default and per-tenant limits imposed by component | |||
| # CLI flag: -validation.max-profile-symbol-value-length | |||
| [max_profile_symbol_value_length: <int> | default = 65535] | |||
|
|
|||
| distributor_usage_groups: | |||
There was a problem hiding this comment.
@bryanhuhta you probably want to provide a similar PR for usage groups.
simonswine
force-pushed
the
20240801_add-docs-for-new-limits
branch
from
675faf5 to
55cd570
Compare
This adds flags for the relabeling rules and also makes sure they will show up in the documentation properly.
simonswine
force-pushed
the
20240801_add-docs-for-new-limits
branch
from
55cd570 to
79a9576
Compare
bryanhuhta
approved these changes
Aug 1, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Aug 5, 2024
This adds flags for the relabeling rules and also makes sure they will show up in the documentation properly. (cherry picked from commit 80e8ad3)
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3462-to-release/v1.7 origin/release/v1.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 80e8ad3320c52ce315114f5db84bb86df707c6e6When the conflicts are resolved, stage and commit the changes: If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-3462-to-release/v1.7
# Create the PR body template
PR_BODY=$(gh pr view 3462 --json body --template 'Backport 80e8ad3320c52ce315114f5db84bb86df707c6e6 from #3462{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.7] chore: Add relabeling rules flags' --body-file - --label 'type/docs' --label 'backport' --base release/v1.7 --milestone release/v1.7 --webOr, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-3462-to-release/v1.7
# Create a pull request where the `base` branch is `release/v1.7` and the `compare`/`head` branch is `backport-3462-to-release/v1.7`.
# Remove the local backport branch
git switch main
git branch -D backport-3462-to-release/v1.7 |
simonswine
added a commit
that referenced
this pull request
Aug 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds flags for the relabeling rules and also makes sure they will show up in the documentation properly.