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

[James Sweeny (JIRA)]

Title: Message Title

James Sweeny commented on an issue   Re: Use a manifest setting in [master] as global manifests What's the current work around for this case? Is it just to set puppet.conf 'manifest' to something static '/our/absolute/manifests/site.pp' and the individual environments have an agreed upon classname convention for a class that always gets picked up from an environment (as I think you described in your first post?) Yep, the current workaround (and I can think of customers who do this) is to not let environments have a site.pp at all, and basically do: modulepath=.../environments/$environment/modules manifest = $confdir/manifests/site.pp In my experience, sites doing this do not classify from site.pp, and use an ENC. If they weren't using an ENC though, I'd think the workaround would be include $::role in the global site.pp or something with hiera_include. 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.