Issue #10109 has been updated by Stefan Schulte.
The problem here is that we can map a resource title to different namevars (with the `title_pattern` method) but puppet has no way to do a backward mapping and looking at the diffs that you attached this seems to be the problem here. Dan Bode did some work on this topic see the discussion [here](http://groups.google.com/group/puppet-dev/browse_thread/thread/82323b06a6de7703) and an experimental patchset which introduces a `namevar_join` method [here](https://patchwork.puppetlabs.com/patch/1178) but I guess none of it made it into core. There are still some other problems when it comes to multiple namevars (#5605), ---------------------------------------- Bug #10109: Composite keys cause Invalid parameter false error https://projects.puppetlabs.com/issues/10109 Author: Brandon Turner Status: Unreviewed Priority: Normal Assignee: Category: agent Target version: Affected Puppet version: 2.7.4 Keywords: Branch: When using a type with more than one name var (composite keys), the agent outputs an error: err: Could not create resource file /var/lib/puppet/state/resources.txt: Invalid parameter false(false) at <filename>:<line> This first appeared in version 2.7.4, most likely in commit:7a39ca72e64. When multiple key attributes exist, `resource.name_var` is false. The new `write_resource_file` method attempts to call `Puppet::Type#[]` with `false` which causes the Invalid parameter error. The new resource list file should support types with composite keys. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. 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-bugs?hl=en.
