This repository was archived by the owner on Jun 5, 2024. It is now read-only.
fix incorrect parsing of action arguments in cscart role #38
Conversation
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
The additional space behind the `=` sign caused Ansible to parse the argument dict incorrectly as follows:
```
{
"password": "",
"{{ lookup('password', playbook_dir + '/credentials/databases/' + item.key.replace('.', '_') + ' chars": "ascii_letters,digits length=16') }}",
}
```
This would cause the task to fail due to an unrecognised parameter. This at least happens on Ansible core 2.13.6 and likely earlier versions too. The fix should maintain backwards compatibility.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The additional space after the
=sign caused Ansible to parse the argument dict incorrectly as follows:This would cause the task to fail due to an unrecognised argument. This at least happens on Ansible core 2.13.6 and likely earlier versions too. The fix should maintain backwards compatibility.
Just out of interest: Why are you using
=for action arguments instead of:?