Details
Description
For Puppet 6, we should prune the language of all vestiges of exporting and collecting, virtual/realized resources.
As far as I can tell, all use cases for these language functions are better handled by various combinations of
- data structures and loops to create resources at the point you need them, with proper resource default propagation for chained dependencies.
- puppetdb query, which lets you find resources without having to specifically export them
- refactoring into roles & profiles that reduce the multiple-declaration problem that realizing was meant to solve
I'd like to collect all the weird edge cases around these constructs as related issues on this ticket, and also solicit feedback on whether there are NOT use-cases that are better covered somewhere else.
Attachments
Issue Links
- relates to
-
PUP-1078 Exported resources are hard to collect by environment
-
- Needs Information
-
-
PUP-1606 put warn/error for attempt to instantiate virtual class under --strict control
-
- Closed
-
-
PUP-1079 Exported resources is exporting to the database with --noop flag
-
- Needs Information
-
-
PUP-3123 One "broken" exported/virtual resource causes all of the same type to fail
-
- Closed
-
-
PUP-5481 Collectors don't match when attribute set by namevar
-
- Closed
-
-
PUP-6014 Default resource parameters are not stored in PuppetDB - not usable in collector
-
- Closed
-
-
PUP-6698 create_resources does not honor '@@resource' as exported resource
-
- Closed
-
-
PUP-4378 Resource collectors can be assigned to variables by abusing chaining statements
-
- Closed
-
-
PUP-3230 Exported resource collectors don't support standard puppet expression set
-
- Closed
-
-
PUP-2217 Improve resource collection to support 'environments'
-
- Needs Information
-
- supports
-
PUP-5945 5.y Language
-
- Closed
-