Deploying Puppet code
-
Built-in deployment policies
Deployment policies are prescriptive workflows for Puppet code deployment that are built into Continuous Delivery for Puppet Enterprise (PE). You select the best deployment policy for your situation, and Continuous Delivery for PE does all the Git heavy lifting for you, deploying your code to the right nodes. -
Creating custom deployment policies
If the built-in deployment policies included in Continuous Delivery for PE don't align with the way your organization works with Puppet Enterprise, you can write a custom deployment policy tailored to your needs. -
Deploy code manually
Use the manual deployment workflow to push a code change to a specified group of nodes on demand. -
Deploy module code
You can deploy new module code to your Puppet environments via a Continuous Delivery for PE module pipeline. To do so, you must first add a:branch => :control_branch
declaration to the module's entry in your control repo's Puppetfile. -
Require approval for deployments to protected Puppet environments
If your organization's business processes require manual review and approval before Puppet code is deployed to certain environments, set up an approval group of individuals with the authority to provide the needed review and sign-off. These approvers are contacted each time a deployment to a protected environment is proposed.