-
Notifications
You must be signed in to change notification settings - Fork 659
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
ansible_args passed to all steps #2963
Comments
My current workaround is to apply tags manually to the converge step, but i would like to avoid this
|
Thanks a lot! |
For those who need to pass config options to all steps and found this issue searching for a solution: Use the config_options in the provisioner section of the molecule.yaml file. I needed to pass a vault-keyring-script to all molecule steps and used ansible_args first, but as stated above that is not intended for this purpose. Do it like this:
|
Issue Type
Molecule and Ansible details
Molecule installation method (one of):
Ansible installation method (one of):
Desired Behavior
I have a particular use case where I want to test a full playbook and it's roles. However, the playbook has to be called with specified tags. I would call the playbook in production like this:
Therefore, I configured my
molecule.yml
like this:I would expect molecule to pass these parameters to the converge step only.
Actual Behaviour
Molecule passes the tags also to create and destroy, which makes my machines never start/stop.
A good create command looks like this
With
ansible_args
it looks like that:The create playbook doesn't do anything with just this tag.
I have reprodiced this with both vagrant and podman driver.
The text was updated successfully, but these errors were encountered: