Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment

[Andrew Parker (JIRA)]

Title: Message Title

Andrew Parker commented on an issue   Re: Make modulepath, manifest, and config_version configurable per-environment The problem with this system is that there isn't any way to express the default configuration, which means that variations of that configuration are also off limits. I'm thinking that this problem could be resolved by extending the settings interpolation syntax to allow referring to other sections of the configuration. For instance if $ {main::modulepath} referred to the modulepath setting as it exists in the main section, then you could write the default configuration of an environment as modulepath = modules:${main::modulepath} manifest = manifests Add Comment   Puppet / PUP-1596 Make modulepath, manifest, and config_version configurable per-environment In order to make the new environment system fully usable, the default modulepath, manifest, and config_version needs to be overridable on a per-environment basis. This is possible in the current system with the environment stanzas and similar flexibility needs to be retained in the directory environments. Each environment should optionally have an {{en... 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/groups/opt_out.