Thanks for your insights. I have not looked into title_patterns in this
case because the name is available in the method and the other namevars are
sufficient for retrieving the other information, though this would allow
for the creation of resources with the same name value with other namevar
Hi Axton,
this is a long-standing issue with how puppet resources are implemented.
Adding path name vars like you did is one of the work arounds with the
least issues. if. you add title patterns, it can be actually quite nice to
use, say, defining for example "/etc/some.conf#key" for the "key" key
What is the best way to implement the get method in a new custom provider
where information from the resource is required when using the Resource API?
Using the management of public or private keys as an example, the get
method cannot return a list of resources without certain information from
