On Tuesday, May 20, 2014 7:36:31 AM UTC-5, Henrik Lindberg wrote: > > This suggests a design that is somewhat inside-out, the idea is that > what is *in* the environment defines what you want, not that you inside > the environment make decisions based on the name of the environment. >
Agreed, and therein may be the workaround that I couldn't come up with. Nevertheless, the observed value of $::environment differs from what the docs say it should be in the OP's case. The only plausible reason for Puppet to provide the $::environment variable at all is so that its value can influence catalog building, whether directly in manifests or by interpolation into hiera hierarchy definitions, or whatever. It's not reasonable to say the variable shouldn't be used according to its docs for its apparent intended purpose. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c8980729-9066-4490-9720-7dc65fd773d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
