Compliance: database tables changes required
Problem to solve
In Review Cells 1.0 design and document Compliance... (#441195 - closed) we analysed the tables owned by groupcompliance mentioned in https://gitlab-com.gitlab.io/gl-infra/platform/stage-groups-index/compliance.html. This was done to determine the next steps changes required to make them Cells complaint.
Here is a list of tables and required changes
Table name | Current gitlab_schema | New gitlab_schema | Comments | Status |
---|---|---|---|---|
audit_events_instance_amazon_s3_configurations | gitlab_main | gitlab_main_clusterwide | Only need to change the schema. |
|
audit_events_instance_external_audit_event_destinations | gitlab_main | gitlab_main_clusterwide | Only need to change the schema. |
|
audit_events_instance_google_cloud_logging_configurations | gitlab_main | gitlab_main_clusterwide | Only need to change the schema. |
|
audit_events_streaming_event_type_filters | gitlab_main | gitlab_main_cell | Need to add namespace_id column to table. | |
audit_events_streaming_headers | gitlab_main | gitlab_main_cell | Need to add namespace_id column to table. | |
audit_events_streaming_instance_event_type_filters | gitlab_main | gitlab_main_clusterwide | Only need to change the schema. |
|
instance_audit_events_streaming_headers | gitlab_main | gitlab_main_clusterwide | Only need to change the schema. |
|
Proposal
Complete required changes on above tables
- For tables which require namespace_id column to be added, will require two migrations:
- Regular migration for adding the new column.
- Background migration for backfilling the values to that column.
Edited by Huzaifa Iftikhar