Fixed t3c for layered profile order issue #7425
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.
when layered profiles are used, t3c was not iterating through the profiles in the proper order,
which was causing duplicate parameters to be incorrectly overridden
Which Traffic Control components are affected by this PR?
t3c
, formerly ORT)What is the best way to verify this PR?
run the unit test for layered profiles, otherwise build and install t3c setup layered profiles on a cache and
have 2 or more parameters with the same config file and name but different values. run t3c and verify
duplicate parameters have been overridden by the profile with the highest priority.
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist