Send fallbackToClosest as a boolean instead of a string #6562
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM if it passes checks |
|
Mind adding a changelog entry @davidc0le ? |
ocket8888
added
ansible
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: #6539
Adjusting the Ansible dataset loader cacheGroup jinja template to send fallbackToClosest ( if provided ) as a boolean instead of a string.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
An example to trigger this is listed with the issue #6539
If this is a bugfix, which Traffic Control versions contained the bug?
5.1.x
6.x
PR submission checklist