Add missing audit event schema
What does this MR do and why?
For more info thread discussion here &8944 (comment 1316827698)
How to set up and validate locally
There is nothing to validate, other then the below checklist Manual Verification for MR assignees.
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.
Manual Verification for MR assignees.
This MR was created using a script and we need to verify the details entered in yml files manually. Also, some of the details need to be manually added eg: the description
field. Please follow the below steps for each file verification
you can remove this block once MR is ready for review.
- Check audit name exists in the codebase.
- Fill description field
- Check introduced_by_issue, This field was parsed from the branch name so for some of the files it should be correct but for some we need to manually fill it up, refer to MR URL to check the related issue.
- Check introduced_by_mr is correct.
- Check milestone is correct.
- Fill feature_category.
- Check saved_to_database and streamed are correct.
Merge request reports
Activity
assigned to @nrosandich
- Resolved by Nate Rosandich
@nrosandich - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request.
added backend groupcompliance typemaintenance labels
added devopsgovern sectionsec labels
3 Warnings ce08b81a: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. This merge request does not refer to an existing milestone. Please add a merge request subtype to this merge request. Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Smriti Garg (
@sgarg_gitlab
) (UTC+5.5)Michael Kozono (
@mkozono
) (UTC-10)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Sincheol (David) Kim
@harsimarsandhu can you please do the initial review on this one?
requested review from @harsimarsandhu
@harsimarsandhu
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.
For more info, please refer to the following links:
added pipeline:mr-approved label
requested review from @dskim_gitlab and removed review request for @harsimarsandhu
mentioned in issue #389692 (closed)
mentioned in issue #389711 (closed)
mentioned in issue #389710 (closed)
mentioned in issue #389709 (closed)
mentioned in issue #389708 (closed)
mentioned in issue #389707 (closed)
mentioned in issue #389706 (closed)
mentioned in issue #389705 (closed)
mentioned in issue #389704 (closed)
mentioned in issue #389703 (closed)
mentioned in issue #389702 (closed)
mentioned in issue #389701 (closed)
mentioned in issue #389700 (closed)
mentioned in issue #389699 (closed)
mentioned in issue #389698 (closed)
mentioned in issue #389697 (closed)
mentioned in issue #389696 (closed)
mentioned in issue #389695 (closed)
mentioned in issue #389694 (closed)
mentioned in issue #389693 (closed)
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Nate Rosandich
- Resolved by Sincheol (David) Kim
Thanks @nrosandich LGTM, but I've noticed some typos. Can you take a look at them and apply my suggestions if they make sense?
removed review request for @dskim_gitlab
requested review from @dskim_gitlab
enabled an automatic merge when the pipeline for 98f07753 succeeds
mentioned in commit 0e601809
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
mentioned in merge request kubitus-project/kubitus-installer!2224 (merged)