-
Notifications
You must be signed in to change notification settings - Fork 7
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
Describe setting parameters in README #2
Comments
Totally agree. I'm always for more documentation. |
If you do the include approach then you can set parameters in hiera. This is the way I usually do it. |
Is there any tool that can generate a simple documentation from Puppet code? So that we would have at least the class signature documented in an easily accessible way. You currently have to go into the source code to find out what the |
There is puppet-strings. I think that is what everyone is using now. |
Note to self: puppetlabs/puppet-strings Do you have an example use, a repo on GitHub that you particularly like? So that we can somewhat copy+paste the configuration. EDIT: Interestingly, a blog post mentioning it was published just today: Self-documenting Puppet modules with puppet-strings |
Some software allows parameters to be set (e.g. software::vcsscm::git).
It would be nice if the README mentioned how those can be set, so that the suggested, preferred way is known (and Puppet newbies are not left in the dark).
Example
Is there a nicer, cleaner way?
include software::vcsscm::git
... is definitely nicer, but how set parameters?
The text was updated successfully, but these errors were encountered: