Have a look in the Settings UI page - there's a setting
called enc_environment which will stop Foreman sending the environment in
the ENC data. Then the client is free to request any environment it wishes.
···On 2 April 2013 23:37, David wrote:
In our legacy puppet 0.25 install (without an ENC), each member of the ops
team could quickly/easily test a puppet deployment of his own modified
puppet tree by using “puppetd --test --environment=$user [–noop]” (we also
have an environment for each person, with modulepath=$user_home/puppet).
That is, we only use either a person environment or a production
environment. After we check our tree works, we commit it to the production
Is it possible to do the same while using puppet 2.6 and foreman 1.1? It
seems that doing “puppet agent --test --environment=$login” doesn’t
override the environment set in foreman (which is set to production).
Setting a person environment through foreman instead of command line seems
to defeat the practicity of our former workflow (plus it doesn’t seem to
work very well for all I tried)