-
Notifications
You must be signed in to change notification settings - Fork 19
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-module-init script #49
Comments
I love this Some initial thoughts
Different classes of modules
Extends (future)
|
I would rather pick a (real) reference module for each class of examples (e.g. Unix, Windows, network, ...) and then make sure that module is the first one that gets update/documented if new ways of working are implemented. That is what I intended with ansible/ansible#20509 The reason for this is that it's easier to see what a best practice is from real examples. Selecting a good reference module is not that easy as the module should not be too complex, but have all the different variants to parameter types, check-mode, diff-mode, warnings, etc. But I prefer real modules over some sort of template, which often go stale or are an afterthought. So maybe yet another ansible command is overkill (and harder for users IMO). |
@dagwieers I agree. Better docs to follow soon :) |
Remark: this is probably achievable using cookiecutter, which would also allow having customizable templates... |
should this be moved to 'devtools' now? |
Proposal:
Author: James Tanner @jctanner IRC: jtanner
Date: 2017/01/26
Motivation
Developers will typically copy an existing module or read through the dev guids to piece together their first module. I want to make it easier and more approachable to get a basic noop module created, via a simple script.
Problems
What problems exist that this proposal will solve?
Solution proposal
Dependencies (optional)
Testing (optional)
Documentation (optional)
Anything else?
The text was updated successfully, but these errors were encountered: