Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Server-set global variables like $::environment get overwritten by client facts Ah, got it now. So a solution would be to simply skip setting the facts as global variables that collide with those set by the server (the "reserved" variables), and instead only store those in the $facts hash. Add Comment   Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environme... 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.