On 19 January 2011 14:40, Patrick <kc7...@gmail.com> wrote: > On Jan 18, 2011, at 7:38 PM, Dan Bode wrote: > > On Tue, Jan 18, 2011 at 7:16 PM, Bostjan Skufca < > bostjan.skufca.w...@gmail.com> wrote: > >> > I work around this by setting a variable in the node definition if I >> > want the client to use an environment other than production by default. >> > My puppet client class then uses this variable value as the environment >> > value in the clients puppet.conf (via a template) >> >> But I want to set it on master for various reasons (mainly security >> and node separation, various environments for various clients (not >> puppet clients, but company clients) which should not be able to see >> other client's stuff by just changing the environment manually). >> > > if you use an external node classifier, you can set it there. > > http://docs.puppetlabs.com/guides/external_nodes.html > > > I don't have the bug report on hand, but I believe that this won't lock > clients out of files and/or plugins in a different environment. > > I actually want to be able to have it the other way around - the node classifier sets the default environment, but my client can override if it so wishes - https://projects.puppetlabs.com/issues/3910
John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
