Issue #12929 has been updated by eric sorenson. Keywords set to telly_deprecation
---------------------------------------- Feature #12929: Deprecate "import" https://projects.puppetlabs.com/issues/12929#change-69083 Author: Nigel Kersten Status: Accepted Priority: Normal Assignee: Nigel Kersten Category: Target version: 3.x Affected Puppet version: Keywords: telly_deprecation Branch: The distinction between import and include/class declaration confuses many users, and we've had a number of edge cases with import that have caused even more confusion. The path forward is to structure your manifests in classes in modules, and to follow autoloader conventions. This does make Puppet much more opinionated, but we believe the benefits are worth it. Particularly this will push people towards a world where Puppet manifests are more easily shareable in the form of modules, and by running everyone through the autoloader, we'll have a much more consistent set of behaviors. We believe there is only one major required use case for `import`, the following pattern: <pre> # manifests/site.pp import nodes/*.pp </pre> where users have separate DSL node definitions in a nodes subdirectory, and wish to import them all. We're committed to solving this use case in associated tickets. If people have other valid use cases for import that the autoloader cannot support, please comment on this ticket. -- 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.
