Set proxies for Code Manager traffic

Code Manager has proxy configuration options you can use to set proxies for connections to your Git server, the Forge, specific Git repositories, or all Code Manager operations over HTTP(S) transports.

Because Code Manager is run by Puppet Server, Code Manager's proxy settings aren't affected by proxy settings in puppet.conf (such as those to Set a proxy for agent traffic).

There are several levels and varieties of Code Manager proxy settings. You can:

• Set the r10k_proxy parameter in the base Code Manager settings , for example:

  puppet_enterprise::profile::master::r10k_proxy: "http://proxy.example.vlan:8080"

  If you set the r10k_proxy parameter, you must use an HTTP URL for the r10k_remote parameter and all Puppetfile module entries.

  The r10k_remote parameter is set when you Enable Code Manager. For information about Puppetfile module entries, refer to Managing modules with a Puppetfile.

• Customize Code Manager configuration in Hiera to set a global proxy for all HTTP(S) operations, specific proxies for Git and Forge operations, or specific proxies for individual Git repositories.

  You can use these settings in combination to override other proxy settings. For example, you can specify a global proxy and a different proxy for Forge operations.

Related information

• Configure proxies