Issue #7790 has been updated by Randall Hansen.
Nick Fagerlund wrote:
> I think a more robust design would be to allow compound blocks (`[agent,
> user]`, or `[dev, testing]`), but that introduces problems of its own. (If
> you do, say, `[agent, production]`, where in the lookup hierarchy do those
> settings live?) We could set it like, environment -> any compound blocks
> including your environment -> run mode -> any compound block including your
> run mode -> main.
We could, at some cost of complexity, use a slightly different syntax that
implies hierarchy:
[ agent -> production ]
[ agent ~ production ]
This might be more explicit should we limit the combinations to two. And
certainly it's a nasty-looking departure from standard array definition syntax.
----------------------------------------
Feature #7790: A new configuration file block that applies to node-based
operations, agent and apply
https://projects.puppetlabs.com/issues/7790
Author: Nigel Kersten
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords:
Branch:
I propose a `[node]` block in the puppet.conf file.
`[main]` propagates to everything, but often you want the same settings to
apply to Puppet in both `[agent]` and `[apply]` run modes.
This would be useful for things like setting reports, storeconfigs, libdir, etc
etc.
--
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.
