Hi Chuck, Looking at the bugs that are linked together for this, I don't see anything that says we had planned on working on this, which is good in that it means I didn't have any false recollections of plans, but bad in that it means we aren't planning on working on this problem.
It looks like the bug that you point to (#5605) has a good discussion about the problem and possible fixes. I'll admit ignorance to the specifics of this case, but would you be interested in trying to tackle this and submit it as a PR against master? On Wed, Apr 24, 2013 at 11:05 PM, Chuck Dand <[email protected]> wrote: > I've been trying to implement a custom type/provider in which I'd like to > use composite namevars. From what I can find support for composite namevars > when using self.prefetch in the provider is a little bit rough at the > current time. I've found a number of posts from Stefan Schulte and Dan Bode > but no conclusion as to if this should be something that now works in > Puppet (right now I'm using v2.7.21) > > > https://groups.google.com/forum/?fromgroups=#!searchin/puppet-dev/5605/puppet-dev/Cr_g2__sX-A/_EhUpiBzR_QJ > > https://groups.google.com/forum/?fromgroups=#!searchin/puppet-dev/prefetch$20composite/puppet-dev/BnBHDS1Ei2U/v8z-6Zd9weMJ > https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/CVYwvHnPSMc > http://projects.puppetlabs.com/issues/5605 > > Only the last of these link suggests to me that no progress has been made > in the 2.7 line, is this something that is likely to be addressed in the > 3.x line? > > More information, in case it is of interest. The type/provider I'm > implementing is for managing Zabbix installations via the Zabbix API. > Composite namevars would allow me to have non-unique > items/discoveryrules/prototypes in discrete Zabbix templates. > > zbx_template_discoveryrule { 'Cisco Controller:APs: .... } > zbx_template_discoveryrule { 'Ruckus Controller:APs: .... } > > where the first part of the title refers to the template the discovery > rule belongs to and the second part would be the specific discovery rule's > name. > > I've successfully managed to create the necessary self.title_patterns and > with that I am able to create the resources with both 'puppet resource' and > via a normal manifest. However once the item is created Puppet can't seem > to determine that the resource already exists and tries to create it again. > I'm presuming this is related to the fact there are multiple key_attributes. > > The design of my type/provider has very much styled upon that described in > Dan Bode & Nan Liu's book 'Puppet Types and Providers' > > Kind regards > > -- > Chuck Dand > > -- > 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 post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/puppet-dev?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Andrew Parker [email protected] Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2013, August 22-23 in San Francisco - * http://bit.ly/pupconf13* **Register now and take advantage of the Early Bird discount - save 25%!* -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
