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.
- Make sure you have super user permissions. You can't create approval groups if you don't have super user permissions.
- If it is not already configured, Configure SMTP for your Continuous Delivery for Puppet Enterprise (PE) installation.
- Identify the users you want to designate as authorized approvers.
- Identify the Puppet environments that need to require manual approval for code deployments.
You can create multiple approval groups if you want different users to authorize deployments to different environments.
-
Create an approval group:
-
Specify which Puppet environments require manual
approval for deployments:
- In the Continuous Delivery for PE web UI, go to .
- Locate the Protected environments section for the relevant PE integration.
- Click Add protected environment.
- Select the Puppet environment for which you want to require manual approval for deployments.
- Select the approval group you want to review deployments to this environment.
- Click Add Protected Environment.
- Repeat these steps to designate additional protected environments, then click Done.
After creating approval groups and designating protected environments, each time a deployment to a protected environment is triggered (either manually or through a pipeline), the members of the environment's designated approval group get an email and a message in the Message center alerting them that a deployment requires manual review.
One member of the approval group must review the deployment's Details page, click Provide approval decision, and choose whether to approve or decline the deployment. If approved, the deployment process proceeds. If declined, the process terminates. A record of the decision is added to the deployment's Details page.