Jira (PUP-1433) Deprecate 'implicit' environment settings and update packaging

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker commented on an issue   Re: Deprecate 'implicit' environment settings and update packaging After talking with Matthaus Owens, it turns out that there are a lot of issues with trying to remove the directories that the current packages create (breaking automation, causing a production environment to just disappear because the new directory environment exists, etc.). It looks like the best way forward on this is to have the RPM and Deb packages create a new directory environment, that isn't named production that serves as an example. This environment could contain a README file that indicates what it is and points a user at some more documentation, but it doesn't have to. The existing /etc/puppet/manifests directories that are created (and any others that we might want to be getting rid of) need to stay around until Puppet 4. Add Comment   Puppet / PUP-1433 Deprecate 'implicit' environment settings and update packaging With the new dynamic environments support, we are no longer going to support an "implicit" environment where the modulepath, manifest and config_version location is set explicitly in Puppet's configuration. Instead, packaging should ensure that the environments directory is populated with a default environment with a site.pp. The manifestdir setting wi... 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.