Vadym, I ran into the same problem and was able to work around as follows with the caveat that it's unsupported:
sudo su - pe-postgres psql \connect pe-classifier select * from groups; # write everything down update groups set environment_name='agent-specified' where environment_name='production'; # then set the last column to 't' if you have any other groups. You may need to specify the override On Saturday, December 27, 2014 7:59:55 AM UTC-8, Vadym Chepkov wrote: > > > > On Saturday, December 27, 2014 9:44:44 AM UTC-5, Martin Alfke wrote: >> >> Hi Vadym, >> >> the PE node classifier is an ENC. >> This ENC sets environments per nodes as an authority. Nodes can no longer >> switch their environments if you use an ENC with environment parameters >> set. >> >> You still have the technical possibility to continue using manifests >> based node classification and therefor you can continue using r10k. >> You will only loose the environment enforcement via ENC. >> >> hth, >> >> Martin >> > > > Hi Martin, > > That's the problem, PE 3.7 creates 'default' group, which can't be edited > and this group enforces 'production' environment for each node. > You can create a new group and override environment there, but you would > have to do it for each single topic branch you create in git and > development team can't work on more than one topic branches from the same > node. This makes development process extremely difficult. > > Regards, > Vadym > > > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/30babbee-4d8e-467e-90ea-c3d0af8f446c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
