Jira (PUP-4413) Error or Warn when environmentpath is enabled and environment is set to master

[Shawn Sterling (JIRA)]

Title: Message Title

Shawn Sterling commented on PUP-4413   Re: Error or Warn when environmentpath is enabled and environment is set to master Let me try and explain a bit better. We had the typical dynamic environments config in our puppet.conf manifest = $confdir/environments/$environment/manifests/site.pp modulepath = $confdir/environments/$environment/modules Saw the deprecation warning in our puppet server logs, so we removed the aforementioned 2 lines and added: environmentpath = $confdir/environments Which appeared to work on every environment but our master environment. When a client tries to run against the master environment, it appears to run against a blank environment. There is no warning on the puppetmaster or client that we are trying to run in an environment who's name is "forbidden". Running both the client and puppetmaster in debug verbose didn't really help to figure out the situation. Renaming our master environment to anything else (other than the other 3 forbidden names) works fine. I'm not asking to fix the restriction on the names, I'm asking that you put a warning/error when someone has the environmentpath variable set on the puppetmaster and is trying to run in a forbidden environment. This will hopefully save someone else from being in the same situation as we were in. Add Comment   This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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.