Migrate from armon/go-metrics to hashicorp/go-metrics #22876
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.
Description
This PR is meant to address #22838. Specifically we are migrating from
github.com/armon/go-metrics
togithub.com/hashicorp/go-metrics
. This is intended to fix downstream dependency imports seen in the issue.(This PR was done with the help of cursor and may need to be verified again)
Testing & Reproduction steps
Verification Tests Passed
✅ Build Success: go build ./... completes without errors
✅ Test Suite: go test -short ./agent/... runs successfully
✅ Binary Creation: Consul binary compiles and runs correctly
✅ Functionality: consul version and consul --help work as expected
✅ Issue Resolution: The original dependency conflict is now resolved - Consul can work with libraries using the new hashicorp/go-metrics path
Links
PR Checklist
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.