[Feature flag] Enable Go implementation of Operations service RPC UserUpdateSubmodule
What
Remove the :gitaly_go_user_update_submodule
feature flag ...
Owners
- Team: Gitaly
- Most appropriate slack channel to reach out to:
#g_create_gitaly
- Best individual to reach out to: Paul Okstad (@pokstad1)
Expectations
What release does this feature occur in first?
### What are we expecting to happen?
Improved memory usage due to the short lived Go subprocess being used instead of long lived Ruby server. Reliability should improve due to each request being isolated to a single process that won't affect other RPCs during failures.
What might happen if this goes wrong?
There may be unaccounted edge cases in how the Ruby client expects the legacy RPC to behave. The Go implementation will need to add test coverage and adjust as needed.
What can we monitor to detect problems with this?
Roll Out Steps
-
Read the documentation of feature flags -
Add featureflagstaging to this issue -
Enable on staging -
Test on staging -
Ensure that documentation has been updated -
Announce on the issue an estimated time this will be enabled on GitLab.com -
Add featureflagproduction to this issue -
Enable on GitLab.com by running chatops command in #production
-
Cross post chatops slack command to #support_gitlab-com
and in your team channel -
Announce on the issue that the flag has been enabled -
Remove feature flag and add changelog entry -
Close this issue
Edited by Paul Okstad (ex-GitLab)