Issue #11629 has been reported by Daniel Pittman.
----------------------------------------
Feature #11629: Track and report origins of duplicate resources when collecting
with StoreConfigs
https://projects.puppetlabs.com/issues/11629
Author: Daniel Pittman
Status: Accepted
Priority: Normal
Assignee:
Category: exported resources
Target version:
Affected Puppet version: 2.7.0
Keywords:
Branch:
When there is an overlap of either local or remote resources in StoreConfigs,
by the standard type and title rules, you end up with an error in your catalog
compilation.
In #11423 we made the error message less confusing, but we should actually
track where collected resources come from and be able to report the exact
source - local, remote, which machines, etc - that causes the problems.
The expected result is that we can have a report that two machines, identified
by their `certnames`, caused duplicate resources - even if they are imported in
separate collect statements. eg:
<pre>
# on host1
@@file { "/tmp/test": ensure => present, tag => "foo" }
# on host2
@@file { "/tmp/test": ensure => present, tag => "bar" }
# on host3
File <<| tag == "foo" |>>
File <<| tag == "bar" |>>
</pre>
...leads to an error that identifies "host1" and "host2" as exporting
overlapping resources, ideally pointing to the exact location in their
manifests that triggers the error.
--
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.
