Jira (PUP-2623) non-environment setup required

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: non-environment setup required Puppet has been using environments under the hood for a very long time. In the "no environment" state before 3.5 and 3.6, you were using the production environment by default, and it happened to not include the environment name in the modulepath and related setting. In 3.6 + it just happens that this default environment is now part of the path and is less hidden. Using /etc/puppet/environments/production/modules is entirely equivalent to using /etc/puppet/modules in that in each case, that path is the modulepath for that specific environment. The directory environments in 3.6 doesn't force you to use environments more than you already have been; it just means that the paths move around a little bit. Add Comment   Puppet / PUP-2623 non-environment setup required Hi everyone, with 3.6, puppet started to deprecate the concept of "non-environment setups" by throwing warnings about a few config-settings and by announcing to remove this kind of setup in future. I am the creator and admin of some kind of multi-master setup, with hiera as the fundamental database. My puppet manifests/modules solely contain "funct... 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.