Jira (PUP-1479) resources using parsedfile providers quietly move resources from default file to target with 'puppet resource'

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker commented on an issue   Re: resources using parsedfile providers quietly move resources from default file to target with 'puppet resource' This affects more than just puppet resource, you can get the same result with a manifest. The analysis of this in redmine 4131 is correct that this is simply a result of the model puppet has of the world. I'm at a loss for how we can solve this and keep puppet consistent. The only reasonable fix that I can think of is to use composite namevars to make host entries in different files unique and then get rid of the target parameter. Add Comment   Puppet / PUP-1479 resources using parsedfile providers quietly move resources from default file to target with 'puppet resource' use the host resource and puppet resource: I expect the following to fail: {noformat} # puppet resource host test1 ensure=present target="/tmp/host" host_aliases=alias1 notice: /Host[test1]/ensure: created err: /Host[test1]: Could not evaluate: ip is a required attribute for hosts host { 'test1':     host_aliases => ['alias1'],     target => '... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.