Workflows and Pipelines can include Approval steps, which require deployments to receive approval before they can proceed.
With Slack approval Integration now any workflow or pipeline that needs approval can be approved via Slack. This reduces the waiting time for approval significantly. As now folks on Collaboration tool like Slack can Approve/Reject the deployment
@CaptainMorgantown We do send some context that is related to current execution of workflow/pipeline.
So if you are looking for lets say which artifact is being deployment as per of current execution. It will come as part of this context.
As you mentioned on Slack, anybody in the designated channel can approve it. Could an option to restrict it to the user group be added do you think? The idea being that we could post the approval to a public deployments channel for visibility and discussion, but still keep the RBAC feature.
I think for now we’ll stick with the notifications only and let users follow the link into Harness for this reason.
+1 to user group restrictions/some sort of permissions. It’s really helpful for our SE team to know when new builds happen but they probably shouldn’t be approving them. We could set up another type of notification for others but seems best to have a single source of truth?