Implement Feature Flag to Disable Integrated Error Tracking by Default
Summary
This issue is to cleanup the <feature-flag-name>
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
Owners
- Team: grouprespond
- Most appropriate slack channel to reach out to:
#g_respond
- Best individual to reach out to: @seanarnold
- PM: @abellucci
Stakeholders
Release Notes
Add a feature flag for integrated error tracking until error tracking is prioritized by product and is production ready.
Expectations
-
Add a feature flag as per https://docs.gitlab.com/ee/development/feature_flags/ -
Return 404
for HTTP endpoints as described in https://docs.gitlab.com/ee/api/error_tracking.html -
Make sure that integrated
is alwaysfalse
in Project Settings API -
Remove the option for error tracking backing in settings, see screen shot -
Update documentation mentioning this feature flag
What might happen if this goes wrong?
Cleaning up the feature flag
-
Create a merge request to remove <feature-flag-name>
feature flag. Ask for review and merge it.-
Remove all references to the feature flag from the codebase. -
Remove the YAML definitions for the feature from the repository. -
Create a changelog entry.
-
-
Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post. -
/chatops run auto_deploy status <merge-commit-of-cleanup-mr>
-
-
Close the feature issue to indicate the feature will be released in the current milestone. -
Clean up the feature flag from all environments by running these chatops command in #production
channel:-
/chatops run feature delete <feature-flag-name> --dev
-
/chatops run feature delete <feature-flag-name> --staging
-
/chatops run feature delete <feature-flag-name>
-
-
Close this rollout issue.
Edited by Alana Bellucci