[Feature flag] Enable sync_traversal_ids

What

Enable the :sync_traversal_ids feature flag ...

Owners

• Team: Access
• Most appropriate slack channel to reach out to: #g_manage_access
• Best individual to reach out to: @alexpooley

Expectations

No visible change. The traversal_ids column on the namespaces table should be synchronized with new namespaces and changes to namespace parent.

What are we expecting to happen?

The namespaces.traversal_ids column to contain data. This column was unused until now.

What might happen if this goes wrong?

The highest risk is of a database deadlock.

What can we monitor to detect problems with this?

Potential logs:

• https://log.gprd.gitlab.net/goto/b2fdadb2687c423fb2b3743e39c590b7
• https://log.gprd.gitlab.net/goto/5473931fd2b87aac8f905cf1b1c5c48f?
• https://log.gprd.gitlab.net/goto/fbf7369dd143127165dc5f3da9809580

PostgreSQL activity https://dashboards.gitlab.net/d/000000144/postgresql-overview?orgId=1

Web error rate https://dashboards.gitlab.net/d/web-main/web-overview?orgId=1

Beta groups/projects

• gitlab-org/gitlab-com groups

Roll Out Steps

This feature flag rollout is part of a larger co-ordinated feature roll out as described in #323312 (closed)

• Enable on staging (/chatops run feature set feature_name true --staging)
• Test on staging
• Ensure that documentation has been updated
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab feature_name true)
• Coordinate a time to enable the flag with the SRE oncall and release managers
  • In #production mention @sre-oncall and @release-managers. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production (/chatops run feature set feature_name true)
• Cross post chatops Slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
• Announce on the issue that the flag has been enabled
• Remove feature flag and add changelog entry. Ensure that the feature flag definition YAML file has been removed in the same MR that is removing the feature flag from the code
  • Remove the query count spec change made at:
    • !52854 (diffs)
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel

Rollback Steps

• This feature can be disabled by running the following Chatops command:

/chatops run feature set --group=gitlab-org sync_traversal_ids false