Issue #12930 has been updated by Nigel Kersten.
Had an in-person chat about this. We don't want to enforce semantics around nodes here, as we're quite frankly unsure about the long term future of the DSL node construct. We don't *know* that it is going away, but we're certainly having thoughts in that direction. There are needs other than nodes here, such as the ability to have a "conf.d" style directory to drop fragments for resource defaults etc, so we want to offer the more general capability. ---------------------------------------- Feature #12930: Provide a manifest directory where all manifests are automatically parsed. https://projects.puppetlabs.com/issues/12930#change-56783 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.
