Skip to content

Add a meaningful audit event name in Project

What does this MR do and why?

This MR adds a meaningful audit event name in Project when ever a project setting is updated

This MR solves:

  1. Add a meaningful audit event name for `suggesti... (#369287 - closed)
  2. Add a meaningful audit event name for `only_all... (#369286 - closed)
  3. Add a meaningful audit event name for `only_all... (#369285 - closed)
  4. Add a meaningful audit event name for `remove_s... (#369284 - closed)
  5. Add a meaningful audit event name for `printing... (#369283 - closed)
  6. Add a meaningful audit event name for `resolve_... (#369282 - closed)
  7. Add a meaningful audit event name for `merge_re... (#369281 - closed)
  8. Add a meaningful audit event name for `require_... (#369280 - closed)
  9. Add a meaningful audit event name for `disable_... (#369279 - closed)
  10. Add a meaningful audit event name for `reset_ap... (#369278 - closed)
  11. Add a meaningful audit event name for `merge_re... (#369277 - closed)
  12. Add a meaningful audit event name for `merge_re... (#369276 - closed)
  13. Add a meaningful audit event name for `packages... (#369275 - closed)
  14. Add a meaningful audit event name for `reposito... (#369274 - closed)
  15. Add a meaningful audit event name for `namespac... (#369273 - closed)
  16. Add a meaningful audit event name for `visibili... (#369267 - closed)

How to set up and validate locally

  1. Setup audit event streaming on a group https://docs.gitlab.com/ee/administration/audit_event_streaming.html#add-a-new-streaming-destination
  2. Create a new project https://docs.gitlab.com/ee/user/project/working_with_projects.html#create-a-project
  3. Check audit event is streamed with correct event name.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #369288 (closed)

Edited by Nate Rosandich

Merge request reports