Fix for Strategies.yaml to include parent_is_proxy and fix some tech debt #7639
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.
Closes: #7638
This PR is to fix an issue where as in #7638, the
strategies.yaml
does not include aparent_is_proxy
value for any servers in the file. This PR also fixes an issue from tech debt where thestrategiesdotconfig.go
is supposed to bestrategiesdotyaml.go
since the file changed from.config
to.yaml
Which Traffic Control components are affected by this PR?
t3c
, formerly ORT)What is the best way to verify this PR?
I have added a test in
strategiesdotyaml_tests.go
, the function isTestMakeStrategiesDotYAMLParentIsProxy
which tests whenopt.ParentIsProxy
is set totrue
and when it is set tofalse
.If this is a bugfix, which Traffic Control versions contained the bug?
I would imagine all existing versions have this issue since switching to
.yaml
structure.PR submission checklist
This PR doesn't need documentation since it has everything already documented in ATS's page. This is just fixing a behavior we were expecting.