t3c: sort peers in strategies.yaml #7182
Merged
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.
During T3C strategy.yaml generation, make sure the peers are sorted by key before writing out. This can cause false positives for reloading ATS.
Which Traffic Control components are affected by this PR?
t3c
, formerly ORT)What is the best way to verify this PR?
With old t3c:
Run t3c. Change a delivery service (header rewrite value, etc).
Rerun t3c. Observe that the strategies.yaml changes due to arbitrary sort order of peers.
Run the same with new t3c and note the peers are now sorted and that a new strategies.yaml file isn't installed by t3c.
If this is a bugfix, which Traffic Control versions contained the bug?
7.1.0
PR submission checklist
[ ] This PR has tests:bug fix[ ] This PR has documentation:bug fix