On 21/02/14 08:41, Joshua Partlow wrote: > Hi folks, > > (TL;DR: in 3.5.0+ environments will change to be named directories with > a specific structure and configurable defaults, all to be found in a > configured 'environmentpath')
Thanks for the detailed explanation Josh, this was really useful. It sounds like a good direction. My only concern is the complete removal of static and dynamic environments in Puppet 4.0, which could be problematic for users who have built workflows around the ability to define complex environment modulepaths. I've been doing a little regression testing and came across the following bug with "puppet apply --modulepath": https://tickets.puppetlabs.com/browse/PUP-1765 Do you have any thoughts on the correct way to resolve this? The current implementation appears unintuitive. My inclination is that the combined loader should treat settings that have been overridden on the command line with higher priority than the environmentpath loader, but environments in puppet.conf at a lower priority. (I suspect in practice, this could be tricky to implement.) -- Dominic Cleal Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/530CBDE3.8080809%40redhat.com. For more options, visit https://groups.google.com/groups/opt_out.
