The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #13675

Import vs autoloading deprecation warning message

Added by Tom De Vylder over 2 years ago. Updated over 2 years ago.

Status:DuplicateStart date:04/06/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:import
autoloading
telly_deprecation
warning

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

I couldn’t find anything related other than a single ticket related to Telly [1] but I might have looked over it.
Anyways it should be documented in more clear and visible way that import should not be used for modules.

I’m still running into customers who still use the following old-fashioned init.pp:

import 'classes/*'
import 'definitions/*'

It seems that a lot of people are not yet aware of the fact that this behavior is about to be deprecated in Telly.
Personally I think people should be warned upfront in the same way as with dynamic look-up deprecation.

Inspired by the dynamic lookup warning message perhaps something along the lines of:

warning: import classes is deprecated. Support will be removed in Puppet 2.8. Use autoloading instead.
Please visit http://doc.puppetlabs.com/autoloading for more information.

[1] https://projects.puppetlabs.com/issues/12929


Related issues

Related to Puppet - Feature #12930: Provide a manifest directory where all manifests are auto... Investigating 03/02/2012
Duplicates Puppet - Feature #12929: Deprecate "import" Accepted 03/02/2012

History

#1 Updated by James Turnbull over 2 years ago

  • Project changed from Puppet Documentation to Puppet

#2 Updated by eric sorenson over 2 years ago

  • Status changed from Unreviewed to Accepted
  • Target version set to 3.0.0
  • Keywords changed from import autoloading deprecated warning to import autoloading telly_deprecation warning

This dropped off my list but yes, should be added for deprecation warnings in Telly.

#3 Updated by eric sorenson over 2 years ago

This won’t start deprecation in 3.0.0 because the solution (a directory of auto-loaded manifest files, #12930) won’t be available by then.

#4 Updated by eric sorenson over 2 years ago

  • Status changed from Accepted to Duplicate
  • Target version deleted (3.0.0)

Also available in: Atom PDF