Issue #7790 has been updated by Daniel Pittman.
>> 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.
I was just talking about this topic: it would be really nice if we
could also set default values for options in the configuration files
for faces, and actions on faces. (Keep in mind that actions and faces
might be user-supplied, so completely unknown to us.)
At the moment we have a proliferation of little configuration file
parsers for faces, which is a sign that this needs urgent attention,
and having a solution that worked not just up here in the scope of the
master, but in the scope of faces and actions, would be great.
As an aside, the configuration model I like the most for this sort of
override is to avoid the problem of syntax entirely:
<pre>
/etc/puppet/${environment}/${face}/${action}/puppet.conf # or just
eliminate '/puppet.' from that
/etc/puppet/${environment}/${face}/puppet.conf
/etc/puppet/${face}/${action}/puppet.conf
/etc/puppet/${face}/puppet.conf
/etc/puppet/puppet.conf
</pre>
Define some clear rules for how things inherit, maybe solve the
"...and back to the default value at this level, even if set below"
problem, and you are golden. :)
----------------------------------------
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.
