On Monday, April 7, 2014 3:03:34 PM UTC+2, Andy Parker wrote: > > On Mon, Apr 7, 2014 at 5:53 AM, Dustin J. Mitchell > <[email protected]<javascript:> > > wrote: > >> On Mon, Apr 7, 2014 at 5:17 AM, Andy Parker >> <[email protected]<javascript:>> >> wrote: >> > Once they are on should it be the behavior that showed up in 3.5.0 >> > (directory -> legacy) or should it have directory envs replace legacy >> envs? >> >> Is there functionality implemented by legacy that can't be replicated >> by directory (at the cost of rearranging some directories, perhaps)? >> From my read, no -- in which case, best to only have one way to >> implement envs. >> >> > 3.5.0 should be able to handle manifests and modules completely. It > doesn't have config_version implemented. 3.6.0 has everything that the > directory environments will support, which ends up making the translation > to them pretty simple in most cases. > >
Really? I have three directories in my modulepath: - modules: this is were I store generic modules - services: this is site-specific modules - forge: modules I have downloaded from the Puppet Forge The services area is an idea I got from <http://projects.puppetlabs.com/projects/1/wiki/Puppet_Best_Practice2>. It is perhaps not as useful today as it once was, since we have hiera today. But I suspect I am not alone in having several areas of modules. Personally, I like having modules I got from external sourced separated from modules I have written myself. It makes it easier to know what I need to upgrade and what I need to take full responsibility for myself. My understanding is that with Directory Environments I'm restricted to a single area. Given that this breaks with a "Puppet Best Practice" document I think this is a severe restriction. (I hope I will be able to use multiple areas in the future as well.) For reference, this is how I set up my modulepath now, after having made changes so that my setup works with Puppet 3.5.0: [master] modulepath=/etc/puppet/environs/$environment/modules:/etc/puppet/environs/$environment/services:/etc/puppet/environs/$environment/forge manifest=/etc/puppet/environs/$environment/manifests/ Yours, /ceder Dustin >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-dev/CAJtE5vQVZrovWuNsQ%3DWCzsOM0O0xMpS_Owp%2BpzM_FtdK-AXXOA%40mail.gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Andrew Parker > [email protected] <javascript:> > Freenode: zaphod42 > Twitter: @aparker42 > Software Developer > > *Join us at PuppetConf 2014, September 23-24 in San Francisco - > **http://puppetconf.com > <http://puppetconf.com/>* > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/7db42ac7-fcd6-4e77-8ba0-2fbf911a2ac5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
