Issue #18551 has been updated by eric sorenson.
Would it be accurate to generalize this request to "Settings should be exposed via REST?" ie. not just the modulepath, but anything in puppet.conf ought to be visible over the network? ---------------------------------------- Feature #18551: REST API should be queryable for modulepath inheritance https://projects.puppetlabs.com/issues/18551#change-94091 * Author: Ken Coar * Status: Needs Decision * Priority: Normal * Assignee: eric sorenson * Category: API * Target version: * Affected Puppet version: 2.7.21 * 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. For more options, visit https://groups.google.com/groups/opt_out.
