-
Notifications
You must be signed in to change notification settings - Fork 666
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
Move https://github.com/retr0h/cookiecutter-molecule #1747
Comments
This cookiecutter template, as used by the tests, is the causing all current build fail, because ansible-lint 4.1.0 introduced new rules. The failing tests are all using the cookiecutter template:
=> same issue with ansible-lint 4.0.1 and 4.1.0 As we want to move forward to ansible-lint 4.1.0, while moving the cookiecutter template, we should ensure that it is used in the tests with non-default values for author, description, company, and that the platforms are defined:
|
[701] Role info should contain platforms => we need to work on that file which does not template platform: https://github.com/retr0h/cookiecutter-molecule/blob/master/%7B%7Bcookiecutter.role_name%7D%7D/meta/main.yml So this ticket becomes a blocker for 2.20. @gundalow can we have some gh/ansible/molecule-cookiecutter ? |
Why creating a new repository when we could host the cookiecutter inside molecule itself? This could save a serious amount of time especially as we test it durin build. Why to risk someone pushing a change to cookiecutter project and break molecule when we can prevent it from start? |
I don't know how the cookiecutter files would be distributed at regular install time of molecule. I guess the current state was adressing this issue: the same command |
Thanks for taking care of this! Local template would be nice but it's a fairly big change (need to write |
Handled in #1749! |
Issue Type
Desired Behavior
https://github.com/retr0h/cookiecutter-molecule.git should be copied inside of github.com/ansible so that we don't depend on external resources
The text was updated successfully, but these errors were encountered: