Issue #5239 has been updated by Sergio Rubio.

Howdy folks,

We've been bitten by this too. If I understand the whole thing correctly, one 
of the problems with the workaround proposed is that you need to patch every 
module that collects exported resources so they do not collision when they're 
used in different environments. Usually, that means forking and diverging from 
upstream at least till the patches are accepted (if they're accepted at all).

Is that correct?
----------------------------------------
Bug #5239: Exported resources are hard to collect by environment
https://projects.puppetlabs.com/issues/5239#change-76405

Author: Jordan Sissel
Status: Needs Decision
Priority: Normal
Assignee: eric sorenson
Category: 
Target version: 
Affected Puppet version: 2.6.2
Keywords: exported resources collection environments
Branch: 


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 all resources in all environments), I have nagios instances 
that try to monitor machines they can't see and thus all checks fail and pager 
goes beep beep. ;)

I found a work around using tags.

<pre>
node default {
  # Globally apply an environment-based tag to all resources on each node.
  tag("deployment::$environment")
  ...
}

# And later ...

SomeResource <<| tag == "deployment::$environment" |>> 
</pre>

The above workaround is sufficient for me to continue deploying exported 
resources (not a blocker).

I was expecting collectors of exported resources would only, by default, get 
resources from the same environment. Barring that, I think a query of <<| 
environment == ... |>> would be quite useful rather than resorting to tagging.


-- 
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.

Reply via email to