Disabling enc_environment per host (#11248)

Josh · August 3, 2015, 1:15pm

Hi,

Does anyone have any feedback on #11248?

The proposal is essentially to allow an 'agent specified' environment for
individual hosts similar to how the PE Console does. This would allow one
to run 'puppet agent -t --environment=feature' on hosts while still
globally enforcing the environment from the ENC (via enc_environment).

Thanks,

Josh

ekohl · August 3, 2015, 1:55pm

There is a --no-environment parameter in node.rb that deletes
environment from the yaml. This is per puppet master (you set
/etc/puppet/node.rb --no-environment in puppet.conf), but

github.com

theforeman/puppet-foreman/blob/master/files/external_node_v2.rb#L344-L351


  Dir.chdir ENV['HOME']
rescue
  $stderr.puts "cannot switch to user #{puppetuser}, continuing as '#{Etc.getpwuid.name}'"
end


begin
  no_env = ARGV.delete("--no-environment")
  watch = ARGV.delete("--watch-facts")

is fairly straightforward. A simple hack would be to parse the yaml and
look for a some marker (parameter?) that strips the environment.

···

On Mon, Aug 03, 2015 at 09:15:53AM -0400, Josh Baird wrote: > Does anyone have any feedback on #11248? > > The proposal is essentially to allow an 'agent specified' environment for > individual hosts similar to how the PE Console does. This would allow one > to run 'puppet agent -t --environment=feature' on hosts while still > globally enforcing the environment from the ENC (via enc_environment).