Backfill instance integrations organization_id
What does this MR do and why?
Set organization_id for existing instance: true integrations via data post deployment migration. It's needed in order to shard this table as part of Cells architecture.
Any newly created instance integrations get organization_id set on creation !186439 (merged). Before we can set not null constraint and set the sharding key - we need to backfill existing records with the organization id. Once done, we should be good with setting not null constraint.
Similar to what's been done for projects !170206 (merged)
Note: .com doesn't have any instance: true integrations. We mainly want to backfill existing instance integrations on self managed instances. We have close to 50 different kinds of integrations with potentially 1 instance version of each, per GitLab instance, so there won't be many writes needed even for self-managed.
Query plans
- Select start: https://console.postgres.ai/gitlab/gitlab-production-main/sessions/39001/commands/119876
- Select end: https://console.postgres.ai/gitlab/gitlab-production-main/sessions/39001/commands/119879
- Update: https://console.postgres.ai/gitlab/gitlab-production-main/sessions/39001/commands/119880
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.