Make enforced [approval_settings] in MR approval rule policies configurable so that specific users can bypass
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
I met with a customer that feels restricted by the default enforced approval_settings from their MR Approval Rule Policy based on how they do deployments in a GitOps project. While they like that they can enforce things like prevent_pushing_and_force_pushing and block_branch_modification - it prevents their deployment process using a Service Account to make a commit to their default branch for a deployment to be triggered. As a workaround they use the API to temporarily remove the compliance framework (associated with the MR approval policy) during the deploy activity and re-apply the framework after it is done. Ideally they would like the ability to add service accounts or specific users as an exception to the enforced approval_settings.