Implemented Cookiecutter #416
Conversation
Use cookiecutter for `molecule init`. Cookiecutter will serve as the foundation for config generation in functional tests, and the skeleton for standardized ansible role management.
| util.print_info("Initializing role {}...".format(role)) | ||
| for template in ['galaxy_init', 'playbook', 'driver/{}'.format(driver), | ||
| 'verifier/testinfra', 'verifier/serverspec']: | ||
| self._create_template(template, extra_context, role_path) |
There was a problem hiding this comment.
I've probably implemented cookiecutter somewhat oddly here. Wanted modular templates, since we need to write an entire role tree with modular test suites. Other times we only want a couple files from the templates.
I figure we can iterate on this, and make it better as we learn more about cookiecutter. 🍪
|
| @@ -0,0 +1,11 @@ | |||
| --- | |||
There was a problem hiding this comment.
I don't get how the variable in the path name works for this file?
There was a problem hiding this comment.
I don't get how the variable in the path name works for this file?
It's a cookiecutter thing. Creates a directory named what we call the repo. In our case the repo is the name of the role we are creating.
|
I don't understand all the nuances of cookiecutter yet, so it's hard to comment on its implementation, but what you've done so far looks clean and logical. |
|
👍 |
Use cookiecutter for
molecule init. Cookiecutter will serve as thefoundation for config generation in functional tests, and the skeleton
for standardized ansible role management.