This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Fix t3c multiple profile generation #7163
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.
Fixes t3c generation when servers have multiple profiles. The bug was a shared loop variable being overwritten in the TO request.
This is a 1-line fix, but it can't be unit tested because the bug was in the actual TO request, and the t3c Integration Tests are still on TO API v3 which doesn't have multiple Profiles. So testing this required updating the framework to v4, which is done in #7167 .
Which Traffic Control components are affected by this PR?
t3c, formerly ORT)What is the best way to verify this PR?
Run tests. Generate config on a server with multiple profiles, verify config is as-expected and all profiles have their parameters applied as-expected.
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist
[ ] This PR has teststests can't be written until the t3c integration framework is upgraded to v3, which is a considerable amount of work[ ] This PR has documentationno docs, no interface change