-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
…3954) # Backport This will backport the following commits from `main` to `8.x`: - [[ReaponseOps] Add name property to audit logs SO (#193323)](#193323) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia","email":"iuliia.guskova@elastic.co"},"sourceCommit":{"committedDate":"2024-09-25T09:34:55Z","message":"[ReaponseOps] Add name property to audit logs SO (#193323)\n\nIssue: elastic/enhancements#19823 the purpose of this PR is to add a rule name to each audit log in\r\nalerting API.\r\nPreviously if with a rule was done some action (like create, delete,\r\netc.), the user could see it in an audit log. But this log included only\r\nrule SO id, but not name. Users wanted to see a rule name associated\r\nwith the audit log.\r\nSo here I added it.\r\n\r\nThe principle I follow here to accelerate development (agreed with\r\n@cnasikas): if it is easy (name easy to extract in the code the\r\n`savedObject`) to pass it. If it is not do not.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"45b4089371f5b7694fde7d08b6a7aaeb70c4a56e","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:prev-minor","v8.16.0"],"title":"[ReaponseOps] Add name property to audit logs SO","number":193323,"url":"#193323 Add name property to audit logs SO (#193323)\n\nIssue: elastic/enhancements#19823 the purpose of this PR is to add a rule name to each audit log in\r\nalerting API.\r\nPreviously if with a rule was done some action (like create, delete,\r\netc.), the user could see it in an audit log. But this log included only\r\nrule SO id, but not name. Users wanted to see a rule name associated\r\nwith the audit log.\r\nSo here I added it.\r\n\r\nThe principle I follow here to accelerate development (agreed with\r\n@cnasikas): if it is easy (name easy to extract in the code the\r\n`savedObject`) to pass it. If it is not do not.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"45b4089371f5b7694fde7d08b6a7aaeb70c4a56e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"#193323 Add name property to audit logs SO (#193323)\n\nIssue: elastic/enhancements#19823 the purpose of this PR is to add a rule name to each audit log in\r\nalerting API.\r\nPreviously if with a rule was done some action (like create, delete,\r\netc.), the user could see it in an audit log. But this log included only\r\nrule SO id, but not name. Users wanted to see a rule name associated\r\nwith the audit log.\r\nSo here I added it.\r\n\r\nThe principle I follow here to accelerate development (agreed with\r\n@cnasikas): if it is easy (name easy to extract in the code the\r\n`savedObject`) to pass it. If it is not do not.\r\n\r\n### Checklist\r\n\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"45b4089371f5b7694fde7d08b6a7aaeb70c4a56e"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Julia <iuliia.guskova@elastic.co>
- Loading branch information
1 parent
36945df
commit 86a065d
Showing
52 changed files
with
344 additions
and
123 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.