Jira (PUP-3069) Use a manifest setting in [master] as global manifests

[Joshua Partlow (JIRA)]

Title: Message Title

Joshua Partlow commented on an issue   Re: Use a manifest setting in [master] as global manifests Sure, James Sweeny, this configuration would use a global site.pp, which could be overridden per directory environment by an environment.conf manifest setting. puppet.conf: default_manifest=$confdir/manifests/site.pp And this configuration would only allow a global site.pp, logging an error if an environment.conf tries to override manifest: puppet.conf: default_manifest=$confdir/manifests/site.pp restrict_environment_manifest=true Henrik has convinced me that either now, or for a 3.7.1, depending on time, we would ensure that the compiler returns an error message if you attempt to produce a catalog for an environment that has been set to override it's manifest, when the main puppet.conf is disallowing it like this one is. The default configuration, would work as directory environments do now, with a default manifest path of $path_to_env/manifests, overrideable by environment.conf. Add Comment   Puppet / PUP-3069 Use a manifest setting in [master] as global manifests In some puppet installations, especially when an ENC is in use, there are not really any environment specific manifests. Instead the ENC controls all of the classes that are included for a node. However, there is still some global setup that needs to take place outside of the ENC. One example of this is globally setting up a filebucket for all file resour... 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.