Using manual Harness approval steps in CD stages
This topic describes how to enable Harness user group(s) to approve or reject a stage at any point in its execution.
During deployment, the user group members use the Harness Manager to approve or reject the deployment manually.
Approvals are usually added in between stage steps to prevent the stage execution from proceeding without an approval.
For example, in a Kubernetes blue green deployment, you might want to add an approval step between the stage deployment step, where the new app version is deployed to the staging environment, and the Swap Primary with Stage step, where production traffic is routed to the pods for the new version.
Other approval methods are:
- Harness Approval stages: Add Approval stages for manual intervention.
- Adding Jira Approval stages and steps: Add Jira Approval stages and steps.
- Adding ServiceNow Approval steps and stages: Add ServiceNow Approval stages and steps.
Here's a manual approval step during the execution of a pipeline:
An approver can approve or reject the step, stopping the pipeline. The approver can also add comments and define variables for use by subsequent approvers and steps.
Here's a quick video that walks you through setting up and running the step:
Here's what a manual approval step looks like in YAML:
name: Harness Approval Step
- name: foo
Add approval step
- In a CD stage, in Execution, select Add Step.
- Select Harness Approval. The Harness Approval settings appear.
Set a default for the step timeout. Leave enough time for the Users in Approvers to see and respond to the waiting step.
The default timeout for an Approval step is 1d (24 hours).
You can use:
For example, 1d for one day.
The maximum timeout duration is 24 days.The timeout countdown appears when the step in executed.
In Approval Message, add the message for the users in Approvers.
Enable the Include Pipeline execution history in approval details option to show approvers the pipeline's execution history. This can help an approver compare the current execution info with historical data.
Enable the Auto-Reject previous deployments paused in this step on approval option to reject old executions waiting for approval when a latest step is approved.Limitations:
- If you have two approval steps in a step group of a stage with the same step identifier, Harness won't be able to differentiate between the approval steps, and rejects previous deployments with the same identifier.
- If you change the services in a CD stage, Harness won't reject the previous pipeline waiting for approval because you added/updated the service in the pipeline.
In User Groups, select the Harness user groups that will approve the step. For more information, go to add and manage user groups.
In Number of approvers that are required at this step, enter how many of the users in the user groups must approve the step.
Prevent approval by pipeline executor
If you don't want the User that initiated the pipeline execution to approve this step, select the Disallow the executor from approving the pipeline option.
Even if the User is in the user group selected in User Group, they won't be able to approve this step.
In Inputs to be provided by approver, you can enter variables and when the approver views the step, they can provide new values for the variables.
If there are multiple approvers, the first approver sees the variables as you entered them in the step. If the first approver enters new values, the next approver sees the values the first approver entered.
A third approver will see all of the variables the first and second approver provided.
The variable values entered by the final approver populate the expressions created from the inputs.
For example, if there were three approvers and you added a Shell Script step that referenced the input variables with an expression, the expression would render the variable values entered by the final, third approver.
You can reference input variables using the
These variables can serve as inputs to later stages of the same pipeline, where they support conditional execution or user overrides.
For example, in a subsequent step's Conditional Execution settings, you could use an expression that only runs the step if the expression evaluates to 1.
<+pipeline.stages.Shell_Script.spec.execution.steps.Harness_Approval_Step.output.approverInputs.foo> == 1
In Advanced, you can use the following options: