Now that r10k has been detailed, let's explore the Puppet Enterprise version of it: Code Manager. Code Manager adds four main features to r10k, as follows:

• File Sync and Rsync across masters from Master of Masters (MoM)
• RBAC and pe-client-tools provides RBAC access
• Automatic environment isolation
• Easy installation

The primary reason to use Code Manager over r10k in Puppet Enterprise is the robust RBAC model provided by Puppet Enterprise. Without Git, r10k hooks require that you log in to the Puppet Master over SSH or the console and run a command to deploy one or more environments. The PE client tools provided by Puppet allow a user to generate a short-lived RBAC access token, which is checked against RBAC in the Puppet Enterprise Console remotely. This remote RBAC model allows you not only to give individuals different levels of access to environment deployment, but it also does not require a user to log in to the Puppet Master at all. The PE client tools are run from a local workstation and deploy the environment through the Puppet Enterprise web API.

The second major feature is file syncing. r10k deploys code directly into the code directory on a single Puppet Master. If an organization has multiple Puppet Masters controlled by a Master of Masters, a single command can deploy the code base to a code-staging directory on the MoM, which will then be deployed synchronously to all Puppet Masters in the environment. Instead of logging in to multiple Puppet Masters, you can run the command once, remotely, and allow the MoM to distribute code across all of your masters.

Code Manager also ensures that all environment isolation commands are run across your system, ensuring that type resources don't accidentally spill over into other environments. The open source equivalent to this command is puppet generate types --environment <environment>.

The final major feature of Code Manager is an easy install. Everything needed to enable Code Manager is self-contained in Puppet Enterprise.