Harness deployment approvals: The alert arrived. Can the approver tell what will deploy?
Harness deployment approvals suit releases that genuinely need someone to give the go-ahead. When evaluating them, do not just check that the notice arrives. Run the same workflow for different services and environments and see whether the approver can identify the actual target from the message or the linked execution record.
A single delivery pipeline can deploy multiple services. If the approval notice only says “Deploy” or “Production release,” the person on call may know there is a request to handle but not whether this run will deploy a new build of the checkout service or release something else. If this is where your team keeps asking for clarification, a Harness approval step can be the formal go-ahead, but first check what information the notice provides.
The Harness documentation says that notices go out while the pipeline is waiting for approval and again when a request is approved or rejected. Seeing a notice does not mean the release got the go-ahead. Even with stage execution details enabled, some fields for later stages may show only an expression when the service, environment or infrastructure is determined at runtime. The documentation recommends placing the resolved values in the approval message.
To evaluate this, start with two fictional approval cards. One simply says “Production deploy”; the other lists the service, environment and planned build version and keeps a link to the execution record. Ask a colleague on call who did not trigger the run to identify what will change. Then check who can approve and whether letting the initiator approve their own request fits your team’s rules. The service and environment are essential to the decision. If the message does not identify them, ask the approver to confirm them in the linked execution record before deciding. An alert that merely arrived does not pass this check.
If your existing CI approval already shows the build and deployment target unambiguously and keeps a clear approval record, there is no need to migrate just to change the alert. Harness is more worth trying when one pipeline serves multiple services and environments. A message that explains what this run will change matters more there than an extra notification channel.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:developer.harness.io