Jira (PUP-2158) Directory Environments breaks many classic Config File Environments

[Per Cederqvist (JIRA)]

Title: Message Title

Per Cederqvist created an issue   Puppet / PUP-2158 Directory Environments breaks many classic Config File Environments Issue Type: Bug Affects Versions: 3.5.0 Assignee: Unassigned Created: 04/Apr/14 6:02 AM Priority: Normal Reporter: Per Cederqvist If you use the script in the classic blog post http://puppetlabs.com/blog/git-workflow-and-puppet-environments you have Config File Environments located at /etc/puppet/environments. Unfortunately, Puppet 3.5.0 will treat them as Directory Environments. If you have a modulepath such as this: modulepath=/etc/puppet/environments/$environment/modules:/etc/puppet/environmentss/$environment/services:/etc/puppet/environments/$environment/forge it will not be used. You have to move your environments someplace else. It is a pity that Puppet 3.5.0 reused the proposed location from that blog post. The transition would have been less painful if another location had been used. Failing that, it would have been less painful if the resolution order had been Config File Enviroment -> DIrectory Environment -> global environment. At the very least, this should be mentioned in the release note and on http://docs.puppetlabs.com/puppet/3.5/reference/environments.html. It was a bit hard to find the resultion order deep down in http://docs.puppetlabs.com/puppet/3.5/reference/environments_classic.html#interaction-with-directory-environments. Add Comment   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.