Client nodes can set the environment, so long as the server doesn't. On Dec 14, 2010 3:21 AM, "Iain Sutton" <iainsut...@gmail.com> wrote: > We have just stumbled across this having moved to external nodes using > Foreman. > > Our dev environment is where we make quick changes to manifests (and > nominally only affect dev nodes), but sometimes those changes are only > relevant to production nodes. In those scenarios, on production nodes we > used to run: > > puppetd --test --noop --environment=dev > > and that would help validate that what we were about to tag would actually > work once it made it to production. Once our dev manifests were correct, we > would make an svn tag and release that to production. > > I've quickly read through the below bug and I can see good arguments for and > against client nodes being able to set the environment, so I'm not sure how > I'd vote. > > How are others approaching this scenario or has everyone just managed to > avoid it? > > Thanks, > > Iain > > > On 11 December 2010 12:59, Nigel Kersten <ni...@puppetlabs.com> wrote: > >> On Fri, Dec 10, 2010 at 12:55 PM, Eric Snow <es...@verio.net> wrote: >> > The issue was that I was not passing the --environment flag during my >> > puppet run. Apparently it ignores the environment returned by the >> > external node classifier. Thanks for all the feedback. >> >> Ahah. I was wondering if you'd perhaps hit that bug. >> >> http://projects.puppetlabs.com/issues/3910 >> >> Feel free to watch it to help us prioritize. >> >> > >> > -eric >> > >> > On Dec 7, 10:15 am, Stefan Schulte <stefan.schu...@taunusstein.net> >> > wrote: >> >> On Mon, Dec 06, 2010 at 03:55:20PM -0800, Eric Snow wrote: >> >> > Thanks for the reply. The modules mount is okay: >> >> >> >> > [modules] >> >> > allow * >> >> >> >> Although a short test with your snippet in my fileserver.conf worked for >> me: >> >> can you try again with an empty fileserver.conf? >> >> >> >> -Stefan >> >> >> >> application_pgp-signature_part >> >> < 1KViewDownload >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> > To post to this group, send email to puppet-us...@googlegroups.com. >> > To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> <puppet-users%2bunsubscr...@googlegroups.com<puppet-users%252bunsubscr...@googlegroups.com> > >> . >> > For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > >> > >> >> >> >> -- >> Nigel Kersten - Puppet Labs - http://www.puppetlabs.com >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-us...@googlegroups.com. >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> <puppet-users%2bunsubscr...@googlegroups.com<puppet-users%252bunsubscr...@googlegroups.com> > >> . >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> . > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
