Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain why specifying ansible extra_arguments doesn't work same as normal ansible #55

Open
ghost opened this issue Jun 29, 2021 · 0 comments

Comments

@ghost
Copy link

ghost commented Jun 29, 2021

This issue was originally opened by @timblaktu as hashicorp/packer#11086. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.


Here it tells users that they need to use an = between key/value in extra_arguments, but it's mysterious why until you look in one of the many past Packer issues related to this, e.g. here or here. I believe the latter link indicates that Packer is doing word splitting by whitespace before passing these to ansible, which is why the args are all wrong and the ansible call doesn't get off the ground.

I believe the description here should explain this, and also suggest that because the whitespace is the problem, users should also be mindful and take care to use quotes around entities containing whitespace."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants