MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/181926+ <!-- The first line of this issue description must be one of the following: 1. `MR: Pending` 2. `MR: <MR link with trailing +>`, 3. If there are multiple MRs: ``` MRs: - <MR 1 link with trailing +>` - <MR 2 link with trailing +>` - ... ``` 4. `MR: No MR` ...and the first description line of the MR should be `Issue: <Issue link with trailing +>` For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#relationship-of-issues-to-mrs --> <!-- The following sections should be filled out as part of the refinement process before the issue is prioritized. For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#2-pre-iteration-planning-meeting --> ## Description Spin off based on the following comment: https://gitlab.com/gitlab-org/gitlab/-/issues/513366#note_2317269171 As part of introducing the`organization_cluster_agent_mappings` table, we plan on renaming `remote_development_namespace_cluster_agent_mappings` to `namespace_cluster_agent_mappings` as the prefix adds no value and makes things long. We plan on following the [zero downtime rename instructions](https://docs.gitlab.com/ee/development/database/rename_database_tables.html) that will spill over two releases ## Acceptance Criteria - [x] add table reference to `TABLES_TO_BE_RENAMED` hash (current release) - [x] add a standard migration to rename the table and pay attention to the **important notes** section in the doc (next release) - [x] modify the models to use the new table name (next release) - [x] add a post migration to remove the view and finalize the rename (next release) - [x] update the `TABLES_TO_BE_RENAMED` hash to remove the table reference (next release) ## Technical Requirements ## Design Requirements ## Impact Assessment ## User Story <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/#-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->