Issue #18551 has been updated by Ken Coar.

Applications that manage Puppet's environments external to Puppet itself -- 
such as git clone updates handled by cron, or a tool to show an inheritance 
chart -- may need this information.

I can see that this wouldn't work as a fact after all, but as a REST API call 
it would be useful.  For example, in our situation we have dozens of 
environments and the inheritance is a nightmare to figure out unless you know 
where to look and how to interpret what you see.  I think it would be a good 
feature to be able to code a script to ask the puppetmaster 'what's the 
modulepath inheritance for module foo' so that it can verify that the 
appropriate resources are available (or absent) in each element of the path.  
For example, the 'development' environment might inherit from 'qa' which might 
inherit from 'production', and being able to predict the origin from which file 
resources will be fetched would be very valuable: sometimes you want them to be 
local to development, but after release you want to nuke those and have them 
fetched from the production path.

I hope that's more clear?

Thanks!

----------------------------------------
Feature #18551: REST API should be queryable for modulepath inheritance
https://projects.puppetlabs.com/issues/18551#change-92823

* Author: Ken Coar
* Status: Needs More Information
* Priority: Normal
* Assignee: Ken Coar
* Category: API
* Target version: 
* Affected Puppet version: 2.7.3
* Keywords: REST API modulepath module_path
* Branch: 
----------------------------------------
If the module environment inheritance path is incorrect, a client can be 
seriously borked when the catalogue is run.  Unfortunately, with Puppet 2.7.3, 
it appears that the only ways to find out what the module path is are:

* Have access to the puppetmaster and find it there
* Run the catalogue on the client.

The feature request here is that the module path be determinable by the client 
through the REST API either:

* as a 'fact' discoverable *via* the `node` or `facts` API path, or
* as part of a new API path that can be queried for configuration information 
that doesn't fall into any other existing catagory.



-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to