Jira (PUP-1078) Exported resources are hard to collect by environment

[Reid Vandewiele (JIRA)]

Title: Message Title

Reid Vandewiele commented on an issue   Re: Exported resources are hard to collect by environment The root problem here is probably that the storeconfigs backend (the supported backend being PuppetDB) doesn't support environments. That means that when resources are exported from any environment, they are stored in a common pool, from which all collectors in all environments then match. We have a story open right now to make PuppetDB environment aware (PDB-24). PuppetDB will need to be environment aware in order to modify the behavior of collectors. The two possible resolutions to this issue, assuming PuppetDB is capable of distinguishing environments, are: 1. PuppetDB isolates environments and resources cannot be collected from other environments. No language changes. 2. PuppetDB isolates environments but we allow resources from other environments to be collected. Language changes will be required. If there are any use cases for #2, then a separate feature request should be filed. Add Comment   Puppet / PUP-1078 Exported resources are hard to collect by environment I noticed today that {{Foo <<| |>>}} collects all Foo resources regardless of environment. Doing {{Foo <<| environment == ... |>>}} would be cool, but I don't think that works. Why was this a problem? I have multiple deployments; some of which cannot see each other on the network (outside of the storeconfigs db). As a result of this behavior (collect a... 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/groups/opt_out.