[Feature flag] Rollout of `packages_conan_allow_empty_username_channel`
Summary
This issue is to rollout the feature on production,
that is currently behind the packages_conan_allow_empty_username_channel
feature flag.
Owners
- Team: Package
- Most appropriate slack channel to reach out to:
#s_package
- Best individual to reach out to: @10io or
#s_package
- PM: @trizzi
- EM: @michelletorres
Stakeholders
n / a
Expectations
What are we expecting to happen?
Conan packages with empty username and empty channel can be pushed to the GitLab Conan Package Registry
When is the feature viable?
When the feature flag is fully enabled.
What might happen if this goes wrong?
Conan packages can't be pushed.
What can we monitor to detect problems with this?
-
https://log.gprd.gitlab.net/goto/2e17e6b15420895bd16066a00fd1cddc
- The amount of
400
responses should be really close to0
- The amount of
What can we check for monitoring production after rollouts?
Amount of 400
responses in https://log.gprd.gitlab.net/goto/2e17e6b15420895bd16066a00fd1cddc
Rollout Steps
Rollout on non-production environments
- Ensure that the feature MRs have been deployed to non-production environments.
-
/chatops run auto_deploy status ba0fb5ab994d1759a7f1dc56543a70a5c32595ee
-
-
Enable the feature globally on non-production environments. -
/chatops run feature set packages_conan_allow_empty_username_channel true --dev
-
/chatops run feature set packages_conan_allow_empty_username_channel true --staging
-
-
Verify that the feature works as expected. Posting the QA result in this issue is preferable.
Specific rollout on production
- Ensure that the feature MRs have been deployed to both production and canary.
-
/chatops run auto_deploy status ba0fb5ab994d1759a7f1dc56543a70a5c32595ee
-
- If you're using project-actor, you must enable the feature on these entries:
[ ]/chatops run feature set --project=gitlab-org/gitlab packages_conan_allow_empty_username_channel true
[ ]/chatops run feature set --project=gitlab-org/gitlab-foss packages_conan_allow_empty_username_channel true
[ ]/chatops run feature set --project=gitlab-com/www-gitlab-com packages_conan_allow_empty_username_channel true
- If you're using group-actor, you must enable the feature on these entries:
[ ]/chatops run feature set --group=gitlab-org packages_conan_allow_empty_username_channel true
[ ]/chatops run feature set --group=gitlab-com packages_conan_allow_empty_username_channel true
- If you're using user-actor, you must enable the feature on these entries:
[ ]/chatops run feature set --user=<your-username> packages_conan_allow_empty_username_channel true
[ ] Verify that the feature works on the specific entries. Posting the QA result in this issue is preferable.
Preparation before global rollout
-
[ ] Check if the feature flag change needs to be accompanied with a change management issue.Cross link the issue here if it does. -
Ensure that you or a representative in development can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the oncall SRE by using the @sre-oncall
Slack alias. -
Ensure that documentation has been updated (More info). -
Announce on the feature issue an estimated time this will be enabled on GitLab.com. -
Notify #support_gitlab-com
and your team channel (more guidance when this is necessary in the dev docs).
Global rollout on production
For visibility, all /chatops
commands that target production should be:
-
Executed in the
#production
slack channel. -
Cross-posted (with the command results) to the responsible team's slack channel (
#g_TEAM_NAME
). -
Incrementally roll out the feature. - If the feature flag in code does NOT have an actor, perform time-based rollout (random rollout).
-
/chatops run feature set packages_conan_allow_empty_username_channel 20
-
/chatops run feature set packages_conan_allow_empty_username_channel 50
-
/chatops run feature set packages_conan_allow_empty_username_channel 70
-
- Enable the feature globally on production environment.
-
/chatops run feature set packages_conan_allow_empty_username_channel true
-
- If the feature flag in code does NOT have an actor, perform time-based rollout (random rollout).
-
Announce on the feature issue that the feature has been globally enabled.
Release the feature
After the feature has been deemed stable, the clean up should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase.
-
Create a merge request to remove packages_conan_allow_empty_username_channel
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 packages_conan_allow_empty_username_channel --dev
-
/chatops run feature delete packages_conan_allow_empty_username_channel --staging
-
/chatops run feature delete packages_conan_allow_empty_username_channel
-
-
Close this rollout issue.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set packages_conan_allow_empty_username_channel false