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

Create production environment directories in packaging

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.0.0
    • Component/s: None
    • Labels:
    • Template:
    • Story Points:
      1
    • Sprint:
      RE 2015-02-25, RE 2015-03-11, RE 2015-03-25

      Description

      In 3.6.0, we are deprecating the implicit manifest dir, and have created example directory environment manifest dirs, but we refrained from removing the deprecated '/etc/puppet/manifests' so as to not break people's systems on upgrade if they happen to be using implicit environments, since a production directory environment would immediately take precedence.

      Now that people have had time to process the deprecation warnings from PUP-1433, we can remove the implicit manifest dir from the rpm puppet.spec.erb and deb puppet-common-dirs.

      Updated

      This ticket has been expanded to include the global manifests and modules directories, and their counterparts in the production environment. The puppet-agent package should no longer create the global manifests directory. But it should create the global $codedir/modules directory, and the $codedir/environments/production/{manifests,modules}/ directories. The latter is necessary to support things like:

      $ puppet module install <name> --environment production
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                joshua.partlow Joshua Partlow
                QA Contact:
                Kurt Wall
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support