explicit type conversion for Ansible 2.20 compatibility#133
Merged
Conversation
Contributor
|
Tested with 2.20.2, and encountered the same exact issue. Manually made these changes on my end, and can confirm this does indeed fix the issue. Also, does not appear to break older Ansible core versions, tested 2.16 and 2.18. All in all, this PR LGTM! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What does this PR do?
Eliminates type conversion errors in user_roles and team_roles, similar to following:
Error while resolving value for 'user_roles_lookvar': Error rendering template: can only concatenate str (not "_AnsibleTaggedInt") to str"
How should this be tested?
Run export.sh using Ansible 2.20 (discovered with 2.20.5)
Is there a relevant Issue open for this?
No