Issue #21702 has been updated by Rob Nelson. Status changed from Unreviewed to Needs Decision
Needs decision from product manager. ---------------------------------------- Feature #21702: Support multiple connection methods in puppet.conf https://projects.puppetlabs.com/issues/21702#change-98446 * Author: James Yale * Status: Needs Decision * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- It specific use cases it would be useful to the puppet client to be able to select from a variety of different connection methods to reach a Puppet Master. The application of this is best shown in the following example: * Puppet client is behind an HTTP proxy, does not have direct access to the Internet / Puppet Master * puppet.conf is remotely managed by Puppet, but is otherwise inaccessible (client is firewalled) * HTTP proxy is changed or removed before puppet.conf is updated to reflect new configuration * Puppet client will never be able to reach Puppet Master to update configuration If http_proxy_host / http_proxy_port were able to support multiple values and could try them (along with direct, no proxy) when attempting to connect in a round robin fashion then an administrator could preconfigure a client for a proxy configuration change without losing connectivity, or rely on the client to fall back to a direct connection. -- 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.
