Hey Oliver :-). > * using class introspection, generate class interface YAML that is > read and used by our ENC instead of using a separate configuration > specification, store this with the versioned Puppet classes.
I guess resource_type is your friend in this case. Info should be available in the REST API guide. Sounds tricky though. > I guess this could constitute a fairly solid argument against the > parameterised class interface benefits I've been arguing for and a > theoretical vote for Hiera ;) Indeed. Hiera or any function could be designed to be more forgiving ... since you can be in control of the class instantiation not Puppet core. Really you would just be solving the problem in similar ways as you defined in your email ... but without hacking core. Benefits/drawback's don't change much - just the methodology becomes easier. ken. -- "Join us for PuppetConf, September 22nd and 23rd in Portland, OR: http://bit.ly/puppetconfsig"; -- 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.
