The good news is, I hope to have a new type/provider combo to submit to the puppet source next week :) Seems like I'm making good progress.
The bad news is, I now need to pick a name that's going to be good for the long haul, before I submit it :) So I'm asking here for suggestions. I'm writing this for what is,as far as I know, a somewhat OS specific feature at the moment. However, perhaps there are vaguely similar features in other OS's I'm not familiar with. Hmm. In some ways, I suppose it's similar to "windows registry". Very similar, really. But at any rate, the particular itch I'm scratching, is I'm writing a module to support what I'd call solaris "system properties", or more SMF properties. Any SMF service, svc:/system/whatever/blah, can have associated "properties" registered along with it.There are some generic properties, and also some service specific properties. For example, most active services tend to have a property named "start/timeout_seconds". It is thus useful to have support, not to install a "new" service, but to finetune existing, already installed system services, with these properties. I thought that I'd use a somewhat portable name, type "sysprop". "systemproperties" seems a bit unwieldy to me, but I dunno. What do you guys think? (FYI, the solaris manpages describe these properties as, "properties in the service configuration repository") -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/V8BB8NkJZ2QJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
