[Feature flag] Cleanup jira_connect_oauth_self_managed
Summary
This issue is to cleanup the jira_connect_oauth_self_managed
feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.
The feature is used to link self-managed instances with the GitLab.com for Jira Cloud app.
Owners
- Team:~"group::integrations"
- Most appropriate slack channel to reach out to:
#g_manage_integrations
- Best individual to reach out to:
@Andysoiron
- PM:
@g.hickman
Expectations
What might happen if this goes wrong?
Users might end up with JiraConnectInstallation records on self-managed instances that need to be cleanued up on case the installation doesn't work.
In case we need to disable the feature again after the release, we can clean up installations with the following script:
JiraConnectInstallation.each do |installation|
next unless installation.proxy?
JiraConnectInstallations::UpdateService.execute(installation, { instance_url: nil })
end
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. -
If not already done, clean up the feature flag from all environments by running these chatops command in #production
channel:-
/chatops run feature delete jira_connect_oauth_self_managed --dev
-
/chatops run feature delete jira_connect_oauth_self_managed --staging
-
/chatops run feature delete jira_connect_oauth_self_managed
-
-
Close this rollout issue.
Edited by Bojan Marjanovic