On 28.01.2014 12:14, Reid Vandewiele wrote:
I don't know the "right" way to do this but I've worked on a couple
of
composite namevar types at least enough that I've seen that kind of
error before.
In effect, when using a composite namevar you must manually specify
how to extract individual parameters from the resource title. It is
assumed that the default title pattern is insufficient.
What happens if for a given resource, no pattern in your
title_patterns matches? Maybe that's what you're running into?
Here are a few other title_patterns examples.
https://github.com/puppetlabs/puppetlabs-java_ks/blob/master/lib/puppet/type/java_ks.rb#L140
https://github.com/reidmv/puppet-module-yamlfile/blob/master/lib/puppet/type/yaml_setting.rb#L166
Not really wanting to sidetrack this thread as it is a topic I've got a
great amount of interest in... But looking at the provided examples it
would appear that
https://github.com/reidmv/puppet-module-yamlfile/blob/master/lib/puppet/type/yaml_setting.rb#L180
is in error and should be :target not :value given
https://github.com/reidmv/puppet-module-yamlfile/blob/master/lib/puppet/type/yaml_setting.rb#L59-63
declares :target as isnamevar while
https://github.com/reidmv/puppet-module-yamlfile/blob/master/lib/puppet/type/yaml_setting.rb#L84-L100
does not list :value as isnamevar at all.
--
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/1186d376588c1c7d7e27ea9add94ded9%40undergrid.net.
For more options, visit https://groups.google.com/groups/opt_out.
