Re: [Puppet Users] Enc forcing environment even passed via command line

2023-01-13 Thread Tejas Bhosale
Hi, Thanks. Any another way can i implement to test my code before pushing to production if i want enc to classify my nodes based on env. On Friday, 13 January 2023 at 14:11:19 UTC+5:30 Martin Alfke wrote: > Hi Tejas, > > Nodes which should not have environment pinning should not have an > env

Re: [Puppet Users] Enc forcing environment even passed via command line

2023-01-13 Thread Martin Alfke
Hi Tejas, Nodes which should not have environment pinning should not have an environment entry set by the ENC. This will allow the agent to switch to any environment. Hth, Martin > On 13. Jan 2023, at 08:37, Tejas Bhosale wrote: > > I am using self written script took as ref from here > > h

Re: [Puppet Users] Enc forcing environment even passed via command line

2023-01-12 Thread Tejas Bhosale
I am using self written script took as ref from here https://github.com/T-Systems-MMS/puppet-example-enc/blob/master/puppet_enc.sh There i am classifying nodes based on env prod and development ... but when i want to make some new changes on development i want multiple people to work there so i w

Re: [Puppet Users] Enc forcing environment even passed via command line

2023-01-12 Thread Martin Alfke
Hi Tejas, It looks like you are using an ENC (https://www.puppet.com/docs/puppet/7/nodes_external.html#comparing_encs_and_node_definitions) This can either be Puppet Enterprise or Foreman. These can force a node to make use of a specific environment only and it forbids switching Puppet environm

[Puppet Users] Enc forcing environment even passed via command line

2023-01-11 Thread Tejas Bhosale
Hi, I have enc script which when executed in output it post environemnt. But for some host when i want to test my changes i want to pass -E on command line like puppet agent -t -E test but that is override by env it gives either development or production env . Can we do anything to fix this