## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/work_items/605425) currently behind the `reindex_vulnerabilities_on_organization_transfer` feature flag. - DRI: @subashis - Team Slack channel: `#g_security-insights` (verify with team) > [!note] > Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. > "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. > [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? Gates enqueuing of `Vulnerabilities::ProcessOrganizationTransferEventWorker` on `Organizations::GroupTransferredEvent`, which fans out `Vulnerabilities::ReindexProjectVulnerabilitiesWorker` jobs to re-index each transferred project's `vulnerability_reads` in Elasticsearch (introduced in !250128). The flag exists so enqueuing only begins once both workers are fully deployed to Sidekiq. While disabled, vulnerabilities of transferred groups keep a stale `organization_id` in ES and appear on the old organization's Security Dashboard. Once enabled, watch Sidekiq queue growth and Elasticsearch indexing load on https://dashboards.gitlab.net — a transfer of a large group tree enqueues one job per project with vulnerabilities. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_security-insights`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set reindex_vulnerabilities_on_organization_transfer 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set reindex_vulnerabilities_on_organization_transfer true --dev --pre --staging --staging-ref ``` **Production** — percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set reindex_vulnerabilities_on_organization_transfer <percentage> --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss reindex_vulnerabilities_on_organization_transfer true /chatops gitlab run feature set --group=gitlab-org,gitlab-com reindex_vulnerabilities_on_organization_transfer true /chatops gitlab run feature set --user=subashis reindex_vulnerabilities_on_organization_transfer true ``` ## Before global rollout Confirm the relevant gotchas before going to 100% — see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) — see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/250128 19.4 /chatops gitlab run feature delete reindex_vulnerabilities_on_organization_transfer --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set reindex_vulnerabilities_on_organization_transfer false # production /chatops gitlab run feature set reindex_vulnerabilities_on_organization_transfer false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete reindex_vulnerabilities_on_organization_transfer --dev --pre --staging --staging-ref --production # remove entirely ```