Bug #15738
Deprecate loading loose-extension filenames for plugins/extensions
| Status: | Needs More Information | Start date: | 07/30/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Andrew Parker | % Done: | 0% | |
| Category: | plumbing | |||
| Target version: | 3.x | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | telly_deprecation | |||
Description
Nigel — This needs some detail, I thought I understood this during the deprecation brainstorming but couldn’t articulate it when taking down notes so it clearly didn’t stick.
History
#1
Updated by Nigel Kersten 11 months ago
- Assignee changed from Nigel Kersten to Andrew Parker
The idea was that extensions should only be loaded from a strict location, i.e. (and this is off the top of my head, I may have some errors here…)
- the type ‘foo’ would only be loaded from lib/puppet/types/foo.rb
- the provider ‘baz’ for the type ‘foo’ would only be loaded from lib/puppet/providers/foo/baz.rb
- the function ‘quux’ would only be loaded from lib/puppet/parser/functions/quux.rb
Now there are some complications here when it comes to facts, as we have a number of dynamically generated facts, where there cannot be a strict mapping between the fact name and the Ruby file that defines them.
I don’t believe we have the same problem with types, providers and functions, but I could be wrong there.
Andy, was that the general idea?
#2
Updated by Andrew Parker 11 months ago
I believe that was what we had discussed. And just to be clear, this means that we would deprecate the fall back to loadall that currently happens. So if we end up falling through to that call, we issue the deprecation warning.