Destroy mutation for google cloud logging configuration
What does this MR do and why?
Describe in detail what your merge request does and why.
Destroy mutation for google cloud logging configuration
This commits adds destroy mutation for google cloud logging configurations
EE: true Changelog: added
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
- Create a google cloud logging configuration using the below mutation
mutation createGoogleCloudLoggingConfiguration {
googleCloudLoggingConfigurationCreate(
input: {
groupPath: "YOUR_GROUP_PATH",
googleProjectIdName: "testing-id-45",
clientEmail: "test@example.com",
privateKey: "sdssssdsaa"}
) {
googleCloudLoggingConfiguration {
id
googleProjectIdName
logIdName
privateKey
clientEmail
},
errors,
}
}
- Now delete this google cloud logging configuration by passing the gid in the below mutation
mutation destroyGoogleCloudLoggingConfiguration {
googleCloudLoggingConfigurationDestroy(input: {
id: "gid://gitlab/AuditEvents::GoogleCloudLoggingConfiguration/ID"
}){
errors
}
}
- After deleting the configuration, Please verify that the Google Cloud Logging configuration we created in Step 1 has been successfully deleted.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #409422 (closed)
Edited by Harsimar Sandhu