Issue #5464 has been updated by James Turnbull.

Status changed from Unreviewed to Needs design decision
Assignee set to Nigel Kersten


----------------------------------------
Feature #5464: It should be possible to process catalogs post compile time
https://projects.puppetlabs.com/issues/5464

Author: Peter Meier
Status: Needs design decision
Priority: Normal
Assignee: Nigel Kersten
Category: 
Target version: 
Affected Puppet version: 
Keywords: 
Branch: 


Based on the discussion in ["optimizing file 
sources"](http://groups.google.com/group/puppet-dev/browse_thread/thread/1c8ac2c2d6fab46#2c8d8baa39d1d717)
 I'm opening this feature request for a general mechanism to process catalogs 
post-compile time.

This would introduce a whole bunch of new possibilities, such as catalog 
optimization, but also catalog verification or double checking of security 
concerns (Aka. "We never want allow to manage the user root").

The idea is more or less that after compilation the master should hand over the 
catalog to a set of configurable "pipes", which are allowed to inspect, adapt 
and change the catalog. After being processed by this "pipe"-set the catalog 
will continue it's further travel down to client (caching, serialization, 
sending down).

These "pipes" should be easily configurable and they should provide an 
convenient interface to inspect, adapt and change the catalog.

Given for example the discussed example in the mentioned thread, such a "pipe" 
could go through all the file resources and remove all sources that are not 
available on the master. This would reduce round-trips to the fileserver 
looking up non-existing file sources.

Another example would be the idea of NigelK that the catalog could become self 
contained that way, that such a "pipe" would add the content of the file 
sources. This would lead to a bigger catalog but would make it easy for clients 
to apply catalogs without network connection.

In the end caching, putting the catalog into a distributed storage, etc. could 
also be done by such a pipe.


-- 
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.

Reply via email to