Deploy Puppet code

Use deployment policies to control how and when code changes are deployed. You can use built-in deployment policies or create your own custom policies. To apply a deployment policy and deploy code, you can either manually deploy code or use pipelines to automate deployments.

Deployment policies can't be triggered on their own. You specify which policy to use when you Deploy code manually or Deploy code automatically with a pipeline. When you set up a deployment, you also specify a repository, branch, commit, environment, or other parameters that determine where to deploy your code, which version of your code to deploy, and how and where the deployment policy operates.

  • Built-in deployment policies
    Deployment policies are prescriptive workflows for deploying Puppet code that are built into Continuous Delivery.
  • Custom deployment policies
    If the built-in deployment policies included with Continuous Delivery don't align with how your organization uses PE, you can write custom deployment policies tailored to your needs.
  • Deploy code manually
    Use the manual deployment workflow to push a code change to a specific node group on demand.
  • Deploy module code
    You can use a Continuous Delivery module pipeline to deploy new module code to your Puppet environments. To do this, you must 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 deploying Puppet code to certain environments, you can create an approval group consisting of users with the authority to review proposed deployments and manually approve or decline them.