----- Original Message ----- > From: "jcbollinger" <john.bollin...@stjude.org> > To: puppet-users@googlegroups.com > Sent: Tuesday, October 16, 2012 3:11:55 PM > Subject: Re: [Puppet Users] Re: Puppet 3.0.0 and Hiera
<snip> >> But parameters expose that info to more than humans -- for example, >> you can use the resource_type REST endpoint today to get a list of >> all classes and their parameters and defaults. Not a lot is using >> that today, but I expect more and more things to start doing >> auto-discovery of parameters, since it's a really machine-friendly >> way to find out what a class "wants." > > > That's an interesting angle of which I was not aware. I'm not sure I > see a use case beyond automatic documentation generation, however, > and there are alternative approaches that could serve that > particular purpose. Do you envision other specific uses? web interfaces that prompts for the right info when someone adds a class to a machine. It would be great if you can set your email client to send plain text emails as per list guidelines. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
