Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2158

Directory Environments breaks many classic Config File Environments

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PUP 3.5.0
    • Fix Version/s: PUP 3.5.1
    • Component/s: Docs, Modules
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      Week 2014-4-02 to 2014-4-09, Week 2014-4-09 to 2014-4-16

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                henrik.lindberg Henrik Lindberg
                Reporter:
                ceder Per Cederqvist
              • Votes:
                5 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support