Op zaterdag 1 februari 2014 02:33:41 UTC+1 schreef Trevor Vaughan: > > +100 for Type/Provider separation. > > I remember the good old days quite well and was really happy when that got > split out. > > Trevor > > The discussion seems to go in the direction of not having a provider. easy_type is by no means at all meant to stop using a provider. Actually, it is by no means a total replacement for the Type and Provider pattern. What it is, is an add-on module for people, less knowledgeable about Puppet (and the intricacies of Types and providers) to have a custom type for an easy kind of resource. Probably only on one kind of OS. That said about the current discussion, what I like about the discussion, is that we seem to all have the idea, it should be easier to make custom types. While we disagree on (at least some) of the directions I took with easy_type. Why not turn this into a discussion on what we would like to see in an easy way to build a type.
I'l start, but please join: - A way to keep it close to people who know about the resource, but less about Puppet - Be able to easy abstract different OS-es and version (Like the current provider - Make it easier to call a set of standard available (and extendable) validators - Make it easier to call a set of standard available (and extendable) mungers. - Make it easy to gradually build the os command by stating a base part and extending it if a property or a name is specified in the resource definition. Bert -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/a1c9c311-a409-47ca-9467-4097f81729f9%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
