Issue #12930 has been updated by Daniel Pittman.
Nigel Kersten wrote:
> You want to push people to put their node definitions in modules?
I am not convinced that nodes belong in the puppet DSL for defining classes,
etc, at all. Separating them out into a separate-but-equal location with a
`node_definition_dir` setting or equivalent would work for me. Which is,
frankly, not much different to defining them in modules.
Alternately, `.../nodes/${fqdn}.pp` works for me, to enable autoloading of node
definitions. At least for the simple ones.
----------------------------------------
Feature #12930: Provide a manifest directory where all manifests are
automatically parsed.
https://projects.puppetlabs.com/issues/12930#change-56656
Author: Nigel Kersten
Status: Investigating
Priority: Normal
Assignee: Randall Hansen
Category:
Target version: Telly
Affected Puppet version:
Keywords:
Branch:
There is at least one major use case where users need to import a set of
manifest files, the following pattern:
<pre>
# manifests/site.pp
import nodes/*.pp
</pre>
As per the parent ticket, we're looking to deprecate `import`, and the most
obvious solution appears to be to offer a configuration option for a directory
where all manifest files are automatically parsed, much like site.pp is now.
This option *does* need to be per-environment.
Randall, I'm looking for input from your team on the user-facing design here,
and if this solution is appropriate, tactical info like the actual name of the
configuration parameter.
--
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.
