Skip to content

Audit event type filters for group level destinations

Hitesh Raghuvanshi requested to merge 436611-event-filters-groups into master

What does this MR do and why?

This MR is introducing audit event type filters for newly introduced top-level group external audit event destinations.

Refer &12339 for the whole proposal and implementation plan.

Migration

up

bundle exec rake db:migrate:up:main VERSION=20240207134321              
main: == [advisory_lock_connection] object_id: 119160, pg_backend_pid: 35864
main: == 20240207134321 CreateAuditEventsGroupStreamingEventTypeFilters: migrating ==
main: -- create_table(:audit_events_group_streaming_event_type_filters)
main: -- quote_column_name(:audit_event_type)
main:    -> 0.0000s
main:    -> 0.0358s
main: == 20240207134321 CreateAuditEventsGroupStreamingEventTypeFilters: migrated (0.0630s) 

down

bundle exec rake db:migrate:down:main VERSION=20240207134321
main: == [advisory_lock_connection] object_id: 118100, pg_backend_pid: 36416
main: == 20240207134321 CreateAuditEventsGroupStreamingEventTypeFilters: reverting ==
main: -- drop_table(:audit_events_group_streaming_event_type_filters)
main:    -> 0.0063s
main: == 20240207134321 CreateAuditEventsGroupStreamingEventTypeFilters: reverted (0.0116s) 

main: == [advisory_lock_connection] object_id: 118100, pg_backend_pid: 36416

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

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

Related to #436603 (closed)

Edited by Hitesh Raghuvanshi

Merge request reports