If you’ve prepared your control repository and Puppetfile, you’re ready to enable and configure Code Manager.
This page walks you through the steps needed to enable, configure, and test Code Manager. When you’re done, you’ll be ready to deploy environments with Code Manager via the command line, a webhook, or a custom script.
You can enable and configure Code Manager either during or after PE installation.
Configuring Code Manager with a fresh PE installation is the easiest method, but you can do this only during a text-mode installation. To enable Code Manager after a new installation or in an existing PE installation, you’ll set Code Manager’s parameters in the PE console.
Note: If you enable Code Manager and file sync, do not attempt to follow the workflows in the Puppet Enterprise Quick Start Guides. The
puppet modulecommand is not currently compatible with Code Manager.
Before you begin, you should have a control repo with a Puppetfile. Additionally, you should have configured the
puppet access command, so that you can generate an authentication token. If so, you’re ready to set up Code Manager.
If you are upgrading from r10k to Code Manager, check the following before enabling Code Manager:
pe_r10kclass. If so, you must remove the
pe_r10kclass in the PE console before moving to the steps below. These steps will provide a standard Code Manager configuration that you can further customize in Hiera as needed.
zack-r10kmodule. Code Manager cannot install or update code properly if other tools are running r10k.
Note that when you start using Code Manager, Code Manager is running r10k in the background. You can no longer directly interact with r10k or use the zack-r10k module.
To configure Code Manager during a fresh installation, add parameters to the pe.conf file. Use these parameters only with text-mode installation, not with web-based installation. Adding the listed parameters enables and configures file sync and Code Manager.
This setting specifies the location of the control repository. It accepts a string that is a valid URL for your Git control repository. For example:
This setting specifies the path to the file that contains the SSH private key used to access your Git repositories. The
pe-puppet user must be able to access this location; we recommend
This SSH private key file, which you created when you set up your control repository, must be located on the Puppet master and owned by the
pe-puppet user. After PE installation is completed, place the key in the specified location. You’ll do this in step 3 below.
The setting accepts a string, such as:
This setting configures Code Manager, the Git control repository to use for storing code, and the private key for accessing your Git repos.
Acceptable values are
false (case sensitive). Set it to
true to enable and configure Code Manager. If you set it to
false, Code Manager and file sync are disabled.
Complete PE installation.
After PE installation is complete, place the SSH private key you created when you set up your control repository in the
Configuration is now complete and you can test the control repo.
To enable Code Manager after installing PE or in an existing PE installation, set parameters in the PE console.
puppet_enterprise::profile::masterclass in the PE Master node group:
true. This enables and configures both Code Manager and file sync.
r10k_remote: This is the location of your control repository. Enter a string that is a valid URL for your Git control repository. For example:
r10k_private_key: This is the path to the private key that permits the
pe-puppetuser to access your Git repositories. This file must be located on the Puppet master, owned by the
pe-puppetuser, and in a directory that the
pe-puppetuser has permission to view. We recommend
/etc/puppetlabs/puppetserver/ssh/id-control_repo.rsa. Enter a string, such as
Run Puppet on all of your masters.
If you run Puppet for all your masters at the same time, such as with the Run Puppet button in the console, you might see errors like this your compile masters’ logs:
2015-11-20 08:14:38,308 ERROR [clojure-agent-send-off-pool-0] [p.e.s.f.file-sync-client-core] File sync failure: Unable to get latest-commits from server (https://master.example.com:8140/file-sync/v1/latest-commits). java.net.ConnectException: Connection refused
You can ignore these errors. They occur because Puppet Server is restarting while the compile masters are trying to poll for new code. These errors should stop as soon as the Puppet Server on the master of masters has finished restarting.
After the Puppet run is complete, test the connection to the control repo.
Because Code Manager is running r10k in the background, you can test the connection to the control repo with a read-only r10k command.
r10k deploy display --fetch
If the control repo is set up properly, this command fetches and displays a list of the environments in the control repo.
Code Manager needs an authentication token for both authentication and authorization. This token allows Code Manager to securely deploy the requested environment.
To generate a token for Code Manager, you’ll first assign a user to the deployment role, and then request an authentication token.
Before you begin, you must configure the Puppet access command line tool.
Before you request a token, you must assign a user the correct permissions with role-based access control (RBAC).
Next, request the token.
Note that by default, authentication tokens have a five-minute lifetime. With the Override default expiry permission set, you can change the lifetime to a duration better suited for a long-running, automated process.
Generate the authentication token using the
On the command line on the master, run
puppet-access login --service-url https://<HOSTNAME OF PUPPET ENTERPRISE CONSOLE>:4433/rbac-api --lifetime 180d.
Enter the username and password of the deployment user when prompted.
The generated token is stored in a file for later use. The default location for storing the token is
~/.puppetlabs/token. To view the token, run
To make sure Code Manager deploys your environments correctly, you should test it. To test, trigger Code Manager on the command line to deploy a single environment.
puppet code deploy my_test_environment --wait
This command deploys the test environment, and then returns deployment results with the SHA (a checksum for the content stored) for the control repo commit. Check to make sure the environment was deployed. If so, you’ve set up Code Manager correctly.
If the deployment does not work as you expect, check over the configuration steps, or refer to the troubleshooting guide for help.
After Code Manager is configured, you can adjust some settings in the master profile in the PE console. These options are required for Code Manager to work, unless otherwise noted.
code_manager_auto_configure: Set to
trueto auto-configure Code Manager.
r10k_remote: The location of the Git control repository. Enter a string that is a valid URL for your Git control repository. For example:
r10k_private_key: Required when using the SSH protocol; optional in all other cases. The file containing the private key used to access all Git repositories. Enter a string, such as ‘/etc/puppetlabs/puppetserver/ssh/id-control_repo.rsa’.
r10k_proxy: Optional. A proxy setting r10k uses when accessing the Forge. If empty, no proxy settings are used.
You can further customize your Code Manager configuration with Hiera.
When Code Manager is fully enabled and configured, you can trigger Code Manager to deploy your environments: