Replies: 2 comments 1 reply
-
|
A partial self-correction - I realized that in option 1, you can avoid a security vulnerability if you apply a branch requirement on the version of the environment that does not have an approval requirement. That would prevent workflow authors from swapping them. However, the points about redundant environment variable/secret management and clunky semantics of what an "environment" is at that point still stand. It's interesting that branch conditions are already supported, but can only be combined with other conditions like approvals using "AND" logic. Really the functionality needed here is just to support "OR" conditions for multiple requirements. |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to add an agreement to this as it's not been replied/actioned in over a year. We require approvals from another dev before merge to I think a newish third option is using a custom deployment rule, but that feels to me like using a hydraulic press to crack a nut and has trust and security implications depending on the service you're using to approve the deployment. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
We'd like to be able to require manual approval to our staging environment from feature branches, but have them automatically proceed when running from the
mainbranch. We allow developers to optionally test in staging from their feature branches, but we want every main commit to go to staging as part of our continuous delivery pipeline.Currently I see no secure way to do this.
I see a couple options to get the desired workflow, but both undermine security and cause other maintenance headaches:
Allowing environments to be configured to bypass approvals for specific branches seems like the simplest and most desirable approach. This still enables the repo admins to control the conditions under which environment access can occur, since they can set branch protection rules that must be met to merge to that branch.
Beta Was this translation helpful? Give feedback.
All reactions