N -- What changed in 2.6.x with regard to functional settings in [environment] > blocks? > > Have we documented the list of functional settings anywhere? > > What settings are currently not functional in an [environment] block and > would be desirable to make functional? >
I'm not sure I under stand what you mean about setting that are "not functional" in an environment block. There are some setting that don't make sense in an environment block, either because they are global to the master or are consumed before the first agent connects (and thus can't be affected by the environment of that argent, or any subsequent agents). Is that what you're referring to? If so, the main thing we did in 2.6.x is refactor to make various settings that are used in compilation but were being cached globally respect environment boundaries. This was an internal structural issue though, and not really a problem with the settings themselves. The settings worked, but the code they controlled had a few bugs that made them less than useful. Does that makes sense, or am I just confused here? -- M ----------------------------------------------------------- When in trouble or in doubt, run in circles, scream and shout. -- 1920's parody of the maritime general prudential rule ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
