Issue #5921 has been updated by Oliver Hookins.
I guess the problem there would be how you effectively bootstrap a blank system, especially if you already assume your modules will be structured in a certain way in order to get your puppetmaster into a running order and serving the module API (when it exists). Aside from that, a JSON-based API would be quite nice. ---------------------------------------- Feature #5921: Allow ENC to dynamically define modulepath/manifest instead of static environments. https://projects.puppetlabs.com/issues/5921 Author: Oliver Hookins Status: Accepted Priority: Normal Assignee: Category: node Target version: Affected Puppet version: Keywords: Branch: I've been told that there are fundamental architectural problems that would prevent this from working right now, in any case I wanted to raise the issue. We have a situation where we have a lot of different modules, and versions of those modules, need to be deployed to various systems. We control this with the modulepath expressed in an environment settings. Unfortunately our environments are growing unwieldy and seem to be an unnecessary middle-man when just wanting to set the correct modulepath for a node. We can adequately figure out our modulepath in the ENC stage, and would like to just pass this modulepath directly to the Puppetmaster for dynamic usage on a per-node-run basis. This would bypass our use of environments altogether. Any thoughts? -- 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.
