Skip to content

Adding tables and models for instance audit streaming destinations

Hitesh Raghuvanshi requested to merge 436602-instance-destinations into master

What does this MR do and why?

Currently we have multiple tables for storing audit events external streaming destinations for an instance. Different tables are for storing configs of different types of destinations, currently custom http, aws and GCP. This change intends to unify all of those tables into a single one for ease and increasing speed of integrations. This part of proposal made in &12339.

  1. As part of this MR, we are adding table and model for storing configs of different types of audit event streaming destinations for an instance.
  2. We will be adding the validations of different types of configs in later MRs.
  3. This MR is quite similar to one created for top-level groups. !141739 (merged)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Migrations

UP

bundle exec rake db:migrate:up:main VERSION=20240130162148
main: == [advisory_lock_connection] object_id: 116380, pg_backend_pid: 17986
main: == 20240130162148 CreateAuditEventsInstanceExternalStreamingDestinations: migrating 
main: -- create_table(:audit_events_instance_external_streaming_destinations)
main: -- quote_column_name(:name)
main:    -> 0.0000s
main:    -> 0.0052s
main: == 20240130162148 CreateAuditEventsInstanceExternalStreamingDestinations: migrated (0.0207s)

Down

bundle exec rake db:migrate:down:main VERSION=20240130162148
main: == [advisory_lock_connection] object_id: 116380, pg_backend_pid: 18417
main: == 20240130162148 CreateAuditEventsInstanceExternalStreamingDestinations: reverting 
main: -- drop_table(:audit_events_instance_external_streaming_destinations)
main:    -> 0.0021s
main: == 20240130162148 CreateAuditEventsInstanceExternalStreamingDestinations: reverted (0.0079s) 

main: == [advisory_lock_connection] object_id: 116380, pg_backend_pid: 18417

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #436602 (closed)

Edited by Hitesh Raghuvanshi

Merge request reports