Issue #7497 has been updated by Nick Moffitt.
Nigel Kersten wrote: > We really do need to rename --noop to something more appropriate. This has me worried. Are you suggesting that I'm using it for something that is against its design, or simply that it doesn't actually perform "no operations" as a CPU NOP instruction would? > If I'm understanding this correctly, noop isn't necessary for this feature > request, it's really just about allowing different storeconfigs settings per > environment? That's a fair assessment of the scope of this, yes. ---------------------------------------- Bug #7497: I would like separate dbnames for staging and production runs. https://projects.puppetlabs.com/issues/7497 Author: Nick Moffitt Status: Needs More Information Priority: High Assignee: Nigel Kersten Category: stored configuration Target version: Affected Puppet version: 2.6.4 Keywords: Branch: I have a database for stored configurations, and all my puppeteers (puppetmasters local to a network segment) have access to speak to that database. When I do my staging runs --noop, however, resources are exported that get collected by production runs. This kind of pollution is extremely dangerous, as stored configurations are the only mechanism we currently have for nodes to communicate configuration status to other nodes. It is highly terrifying to see a front-end server start serving requests to a back-end server that only ever went through a --noop configuration run. I tried putting a "dbname = staging" in my [staging] stanza, but it appears that I can't have different environments speaking to different databases (even on the same server!). It would be extremely helpful if this were possible. -- 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://projects.puppetlabs.com/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.
