Skip to content

[Feature flag] Cleanup github_user_mapping

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

This issue is to cleanup the github_user_mapping feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production.

It has been enabled on production during 17.8 with no issues. We are cleaning up the feature flag with this issue as the feature is now 100% rolled out and 'productized'.

Let's make sure to also clean up our docs, i.e., remove any mention of this flag and the deprecated user mapping approach in our docs.

Owners

Expectations

What might happen if this goes wrong?

If there is an issue with the implementation on our side, Github imports may fail and/or user contributions will be mapped incorrectly. Import failures are logged, and the log event includes information about the relevant import stage.

Cleaning up the feature flag

  • Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup
  • Create a merge request to remove github_user_mapping 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 <feature-flag-name> --dev --pre --staging --staging-ref --production
  • Close this cleanup issue.
Edited by 🤖 GitLab Bot 🤖