-
Notifications
You must be signed in to change notification settings - Fork 667
plugins: add role name to vars context for embedded converge.yml use case #2675
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
Comments
Continuation of #2671. This will mean you really can use only |
I am ok with it. I have some concerns regarding the fact that this may promote lack of real testing from some lazy users. In the end, they are supposed to add something inside Overall, decent defaults that lower the total number of files needed to added are making much easier to adopt the tool. Keep in mind that sometimes we do not have a role, not all scenarios are hosted inside a role. When implementing this, be aware of this instead of creating a confusing error about a non existing role. |
I am closing this ticket as this is an unlikely use-case and no is expected. Still, keep in mind that a closed ticket does not mean a PR would not not be welcomed, it only means to not expect anyone else to implement it for you. |
Desired Behavior
The default cookiecutter defined
converge.yml
is:Now, if you don't include a converge.yml in your molecule/default and your plugin provides a playbooks/converge.yml file then molecule will load that embedded playbook.
However, we can't embed that in a playbooks dir in the plugin packages because it will not know what the cookiecutter variable is when it is used.
So, we need to inject the role name variable into the context here for this use case.
Seems simple to do.
The text was updated successfully, but these errors were encountered: