Tech Eval: Deployment Approvals

Topic to Evaluate

Deployment Approval is one of the upcoming big features in ~"group::release". We already have a vision from UX/UI perspective and backend/system perspective. This issue is to make sure that these proposals can be fitted together in order to execute the plans without worrying potential re-work.

In this issue, we try to build a prototype of #342180 (closed) and evaluate the feature on a hypothetical situation (based on #342180 (closed)):

• There is a project with Continuous Deployment setup.
• There are two operators in a project - Operator-A and Operator-B.
• Operators want to require an approval on deployment. Only both Operator-A and Operator-B have agreed upon the deployment, the project executes the deployment job.
• Operators can check the approval history - who/when approved/rejected which deployment.
• If a deployment is rejected, the pipeline job fails with a clear message.

We demonstrate the scenario in a sync call, summarize the concerns and decide if we go down the path.

Tasks prior to evaluation

• Clearly document the topic to evaluated in this issue description
• Determine specific scope including time-bounds for investigation

Tasks to Evaluate

• Determine feasibility of the feature
• Create issue for implementation or update existing implementation issue description with implementation proposal
• Set weight on implementation issue
• If weight is greater than 5, break issue into smaller issues