Issue #2748 has been updated by Markus Roberts. Status changed from Needs design decision to Accepted
After a long discussion on the dev list (http://groups.google.com/group/puppet-dev/browse_thread/thread/acc6f33e332cbfa0) the consensus seems to be Alan's suggestion from #10 above--have the client provide it's choice and allow the server to override it. This should be reasonably straight forward for most config settings except for the environment, which will require some attention to detail, as the client will make the initial request with respect to the environment which it believes it is in--and the server will have to be cognizant of this. ---------------------------------------- Bug #2748: config file takes priority over external_nodes in 0.25.x http://projects.reductivelabs.com/issues/2748 Author: Bart Verwilst Status: Accepted Priority: Normal Assigned to: Markus Roberts Category: Target version: 0.25.2 Affected version: 0.25.1 Keywords: Branch: When using 0.24.8, we have a puppet.conf file for our clients that contained this amongst others ): [main] environment = production environments = production, staging This caused the default environment to be production, but we could force the staging environment by making the external_nodes output look like this: parameters: environment: staging It would then execute everything from the staging tree, as expected. Since we switched to 0.25, we noticed that this method no longer works. We always sync to production, no matter what is given in the external_nodes output. Apache logs say "GET /production/catalog/mail01.netnoc?facts=--...", making it always fetch from production. When changing puppet.conf on the client to read environment = staging, then it fetches "GET /staging/catalog/mail01.netnoc?facts=--...", bringing in the right tree. I guess i could make this work by changing the puppet.conf file to a template and have environment = <%= environment %> inthere, and making puppet restart itself when this file is changed ( we run puppet from a cron, not as a deamon ), but still it's a nice piece of functionality that's disappeared now :( -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
