Add t3c flag for local ATS version for config gen #7032
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.
Adds a new
t3c-apply
--local-ats-version
flag to discover and use the local installed ATS version for config generation, rather than the Traffic Ops Serverpackage
Parameter.This, combined with the existing
--install-packages=false
flag, allows users to manage the ATS operating system package with an external tool (e.g. Ansible, Puppet, etc).Which Traffic Control components are affected by this PR?
t3c
, formerly ORT)What is the best way to verify this PR?
Run tests. Run t3c-apply with the new
--local-ats-version
flag with a local installed Traffic server major version different from any Server Package Parameter, verify local ATS version is used to generate rather than package Parameter.If this is a bugfix, which Traffic Control versions contained the bug?
Not a bug fix.
PR submission checklist