New processor to notify feature flag MR that got deployed
requested to merge 1403-new-processor-to-inform-authors-of-ff-controlled-feature-that-their-mr-got-deployed-to-canary into master
What does this MR do and why?
This new processor will notify the author of a feature flag merge request when it gets deployed to an environment. This removes the need for authors to "poll" environments to check when their change is deployed.
Expected impact & dry-runs
These are strongly recommended to assist reviewers and reduce the time to merge your change.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-
Closes #1403 (closed).
Edited by Rémy Coutable