Removes interaction with EOC and Release Managers as a step to FF rollout
What does this MR do?
Proposes a change to the Feature Flag Roll Out
template removing the need to get a go-ahead from the engineer on call and release manager. Related to gitlab-com/gl-infra/delivery#1473 (closed)
The EOC has been tagged as a human-based check point to ensure operational safety, but now that ChatOps has an automatic stop when an incident is ongoing, this removes the need for this check. Additionally getting the EOC to review requires context the SRE may not have and likely does not have time during their shift to build.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Brent Newton