Update audit events streaming destinations graphql to handle active flag
What does this MR do and why?
Add backend API changes for marking a streaming destination as active or inactive through Update requests It also skips a frontend test suite as the frontend is not implemented yet.
- 3rd MR of 4
GraphQL Schema Updates (~10 files)
Added active: Boolean field to all destination types in the schema Added active argument to all update mutation inputs Updated GraphQL interfaces to include the new field
Mutation Logic Updates (~8 files)
Added active parameter to all update mutation resolvers Updated mutation logic to handle the new active attribute
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
Use active as part of graphql endpoints:
Group-level destinations:
auditEventsAmazonS3ConfigurationUpdate externalAuditEventDestinationUpdate googleCloudLoggingConfigurationUpdate groupAuditEventStreamingDestinationsUpdate
Instance-level destinations:
auditEventsInstanceAmazonS3ConfigurationUpdate instanceAuditEventStreamingDestinationsUpdate instanceExternalAuditEventDestinationUpdate instanceGoogleCloudLoggingConfigurationUpdate
With active: true or active: false
When false, it should not stream audit events.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.