feat: change alertmanagerAPIPath to v2 #7928
Closed
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.
What this PR does
This change responds to the recent Alertmanager upgrade, where the deprecation of the
api/v1
path was announced in version0.27.0
Alertmanager-PR2970. From version0.28.0
, Alertmanager plans to drop this path, hence I am making this small change for Mimirtool, which currently uses the deprecated path.The new Mimir version
2.12.0
also announced a change to the Alertmanager V1 API in the changelog, so it seems appropriate to have this change ready for the next release.Which issue(s) this PR fixes or relates to
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.