On Wed, Nov 14, 2012 at 9:44 AM, fatmcgav <fatmc...@gmail.com> wrote:
> However I'm not sure that having individual params/properties for each > volume option is the right way - The list of possible volume options > currently stands at 36.. I don't really fancy having to implement a > param/property for each of those... However I could see a single 'options' > hash param/prop working for that... Although then I'm back to the same > challenge of making sure each volume option is set & maintained > correctly... > Creating 36 options is a bit of work, but they will be documented as resource properties, and puppet takes care of some of problem of which option needs to be updated and only call the setter for a specific option when necessary. I suspect the option values getter/setter are very similar so you can use define_method to reduce boilerplate code. Certainly you can create a single property with a hash value to manage all 36 options, but in this case the option property need to do a few extra things: 1. option method should return all 36 options in a hash. 2. insync? should return true as long the user specified subset of option values is the same as the one returned by the previous method. It might make sense to maintain the list of option that needs to be updated for the setter method. 3. option= should determine which options need update and perform them. The other challenge is that to set volume options is a different webservice > call to the volume-list/volume-create method, but I'm guessing I can just > get that handled with another def in the provider... > If it makes sense to have them in one resource, whether it's one or more api call is just something the provider abstracts away. I wouldn't be concerned how many api/commands the provider uses to manage a resource. HTH, Nan -- 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.
