Hi all, I am using puppet with an ENC script. In this scripts YAML output the environment (generally "production") is set. For testing purposes I would like to start puppet runs from the cmdline of a managed host like: $ puppet agent --onetime --no-daemonize --verbose --no-splay --environment development The problem is the --environment Parameter is not being used if an environment is already set in the ENC. The ENC environment settings seems to always win over the cmdline. Is the the desired behavior? I would like to set all configuration (incl. environment) in the ENC, but want to be able to override it from the cmdline. (BTW: switching the environment from the cmdline works, when I remove the line from the ENC.) Thanks and bye, Frederik -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Jun 22, 2011 at 7:15 AM, Frederik Wagner <fnerdwq@googlemail.com>wrote:> Hi all, > > I am using puppet with an ENC script. In this scripts YAML output the > environment (generally "production") is set. > > For testing purposes I would like to start puppet runs from the > cmdline of a managed host like: > $ puppet agent --onetime --no-daemonize --verbose --no-splay > --environment development > > The problem is the --environment Parameter is not being used if an > environment is already set in the ENC. The ENC environment settings > seems to always win over the cmdline. Is the the desired behavior? >It is, but there are some complications as this bug shows: http://projects.puppetlabs.com/issues/3910> I would like to set all configuration (incl. environment) in the ENC, > but want to be able to override it from the cmdline. > (BTW: switching the environment from the cmdline works, when I remove > the line from the ENC.) >The plan is to allow the client-specified environment to be exposed to the ENC, and then in your ENC you can make the choice between using that, or specifying an environment centrally.> > Thanks and bye, > Frederik > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- Nigel Kersten Product, Puppet Labs @nigelkersten -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Nigel, ah yes, thanks. I think I just ran into the problem people were mentioning at puppetcamp... oops. Now I finally get it ;-) Thanks, Frederik On Wed, Jun 22, 2011 at 7:08 PM, Nigel Kersten <nigel@puppetlabs.com> wrote:> > > On Wed, Jun 22, 2011 at 7:15 AM, Frederik Wagner <fnerdwq@googlemail.com> > wrote: >> >> Hi all, >> >> I am using puppet with an ENC script. In this scripts YAML output the >> environment (generally "production") is set. >> >> For testing purposes I would like to start puppet runs from the >> cmdline of a managed host like: >> $ puppet agent --onetime --no-daemonize --verbose --no-splay >> --environment development >> >> The problem is the --environment Parameter is not being used if an >> environment is already set in the ENC. The ENC environment settings >> seems to always win over the cmdline. Is the the desired behavior? > > It is, but there are some complications as this bug shows: > http://projects.puppetlabs.com/issues/3910>> >> I would like to set all configuration (incl. environment) in the ENC, >> but want to be able to override it from the cmdline. >> (BTW: switching the environment from the cmdline works, when I remove >> the line from the ENC.) > > The plan is to allow the client-specified environment to be exposed to the > ENC, and then in your ENC you can make the choice between using that, or > specifying an environment centrally.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Maybe Matching Threads
- Trouble with ENC and static.pp : enabling ENC fails to find node even with default node in site.pp
- My ENC won't work, YAML is valid AFAIK
- ENC paramater interpolation in ENC, and inline templates
- The quantum effect when loading classes
- Class parameter flexibility with ENC, hiera or both