Skip to content

Migrate HTTP and GCP destinations using workers

Andrew Jungrequested to merge
457623/http-gcp-destination-migrate-worker into 457623/aws-destination-migrate-worker

What does this MR do and why?

Follow up to !179276 (closed), to migrate the remaining categories: http, gcp

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

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.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

  • Open rails console
  • Create rows in:
    • audit_events_external_audit_event_destinations
    • audit_events_instance_external_audit_event_destinations
    • audit_events_google_cloud_logging_configurations
    • audit_events_instance_google_cloud_logging_configurations
  • Run the workers (MigrateHttpDestinationsWorker, MigrateGcpDestinationsWorker)
  • Check the audit_events_group_external_streaming_destinations and audit_events_instance_external_streaming_destinations tables; there should be rows with the equivalent data created and mapped by ID (legacy_destination_ref)
  • The old table rows should now have a stream_destination_id that maps to the newly created row.

Merge request reports