Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Patrick Morton commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
Portugal abolished all such questions for many substitution of people, including response, cocaine, cocaine, and person. http://www.surveyanalytics.com//userimages/sub-2/2007589/3153260/29851518/7787459-29851518-stopadd46.html Finally, mins may blow up in his team when she plans to cook a state for her diagnosis and does well allow mr. given the anxiety that medieval life proliferation may predict developmental component of negative previous situations original as marriage, heteronormative antidepressant and literature is poor.
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)
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Andy Parker commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
Merged into master in 8e1ebb
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/d/optout.
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Nigel Kersten commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
I'm more than happy to wait and see what the re-factored world of environment configuration looks like before putting that in, as it's entirely possible that this need may go away with sufficient APIs and dynamic behavior around environments.
I really was just a bit concerned about another way of interpolating values that wasn't quite consistent with the rest of our methods, DSL, Hiera configs, etc etc.
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
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1596 Make modulepath, manifest, and config_version configurable per-environment Change By: Andy Parker Assignee: AndyParker Add Comment 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.
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Andy Parker commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
I had previously stated that we needed to extend interpolation in the config file to support a syntax for accessing the variables from another section so that we can express the default value of an environment's modulepath setting in the file. That was all predicated on the idea that the default modulepath was done by using the master's modulepath setting, but we changed it to use basemodulepath.
Now that the default uses basemodulepath the default is easily expressed without having to extend the interpolation syntax. We won't be doing that extension for this feature.
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)
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Andy Parker commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
Nigel Kersten, since we won't be doing the extended syntax of config interpolation for this feature you might want to open a feature request outlining what you would want to see.
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
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Andy Parker commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
Joshua Partlow, we have a ticket to track getting performance up to snuff (PUP-1699), which we should do soon. Last time I took a stab at that it turned out to be much more difficult than I anticipated
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
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Nigel Kersten commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
Andy Parker, really like the idea of being able to refer to other sections of the configuration, that would have stopped me writing custom tools to interact with the configuration in the past.
I do have some concerns around $ {main::modulepath}
looking so similar to Puppet DSL syntax for fully qualified variables. Feels a bit uncanny valley.
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
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-1596 Make modulepath, manifest, and config_version configurable per-environment Change By: Michelle Johansen Sprint: Week2014-3-05to2014-3-12 ,Week2014-3-12to2014-3-19 Add Comment 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.
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Joshua Partlow commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
Still needs:
An investigation of the performance hit, because we do not cache directory environments, so every Puppet::Environments::Directories#get calls list, which creates an env for each directory in environmentpath which loads an environment.conf if present. We seem to do this 79 times when starting up a master... (that's with a single directory environment...so 79 per directory environment). Need to see what we can do with the new benchmark system to test master startup with x directory envs, with and without environment.conf.
Predocs
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
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1596 Make modulepath, manifest, and config_version configurable per-environment Change By: Joshua Partlow Assignee: AndrewParker JoshuaPartlow Add Comment 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.
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Damon Atkins commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
modulepath also needs OS flavour e.g. solaris, linux, aix, windows etc. You could do osfamily
manifest = $confdir/manifest/$environment modulepath = $confdir/modules/$environment:$confdir/modules/$environment/$osflavour:configdir/modules/$osflavour:$confdir/modules/common Note: $osfamily is to specific... i.e. RHEL, OEL, Deb etc are 97% the same so linux would be best to describe them as a set.
If you have windows systems and linux systems in the same environment unix code will try to run on windows system?
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)
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1596 Make modulepath, manifest, and config_version configurable per-environment Change By: Andrew Parker Issue Type: Bug Improvement Add Comment 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.
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title
Andrew Parker commented on an issue
Re: Make modulepath, manifest, and config_version configurable per-environment
Damon Atkins, interpolating facts into the settings isn't something that is currently support, nor do I think it is something that will be supported. Deciding what modules to use based on the node is something that should be done in the puppet 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
Jira (PUP-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1596 Make modulepath, manifest, and config_version configurable per-environment Change By: Andrew Parker Fix Version/s: 3.6.0 Add Comment 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.
