Hi Vadym, The new classifier does allow agents to specify their own environments, but it involves an extra couple of steps. What you'll want to do is create a new group for the nodes that you're concerned with (which could be all of them) and set the environment of the new group to "agent-specified" in the pulldown menu. If you never want to override that setting with another classifier group, then you should also set "Override all other environments" in the group's metadata.
Hope that helps! Justin On Friday, December 26, 2014 3:39:02 PM UTC-8, Vadym Chepkov wrote: > > Hi, > > I really hope I am mistaken, but it seems you can't use r10k with it's > full potential anymore in Puppet Enterprise 3.7. > > In the past (PE3.3) I could create any branch, feature_something, in git > repository. r10k would create a branch/environment > > and I > > could > > apply it from the command line on some development host, i.e. > > puppet agent -t --environment=feature_something > > Now, according to puppetlabs support, "console node classifier being the > definitive and authoritative environment-setter", so I can't do that > anymore. > This seems like a major setback and a deal breaker for me. Does anybody > else use environments this way? > > Why even have --environment switch altogether if I can't select anything > besides what is set in the console. > > What are other choices except ditching PE altogether? > > Thanks, > 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/783f0d46-3222-418f-8d56-19ee6423f006%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
