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
…4010) # Backport This will backport the following commits from `main` to `8.x`: - [[Entity Analytics] Asset Criticality soft delete (#193591)](#193591) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Vila Verde","email":"tiago.vilaverde@elastic.co"},"sourceCommit":{"committedDate":"2024-09-25T13:54:30Z","message":"[Entity Analytics] Asset Criticality soft delete (#193591)\n\n## Summary\r\n\r\nThis PR introduces a \"soft delete\" for Asset Criticality records.\r\nInstead of deleting the document, we now simply change the criticality\r\nfield to the value `\"deleted\"`.\r\nThis value is fully managed on Kibana and should not be exposed to the\r\nclient side.\r\n\r\n\r\n### How to test\r\n\r\n1. Add some host/user data\r\n2. Make sure to enable the `entityStoreEnabled` feature flag\r\n3. Assign asset criticality to a user/host.\r\n* You may need to enable Asset Criticality in Kibana Advanced Settings\r\n5. Verify the criticality has been assigned by `GET .asset-citicality*`.\r\n6. Unassign the criticality for that host/user via the UI.\r\n7. `GET`ing the criticality index should now still show the updated\r\nrecord with `\"deleted\"` criticality value\r\n8. The Ui should also show criticality as `Unassigned` for the deleted\r\nrecord.\r\n\r\n\r\n\r\nImplements elastic/security-team#10531, which\r\nis part of the overall [Entity Store for\r\n8.16](elastic/security-team#10529) work","sha":"a8c7e0659635994546874fb1f7ec1304fa4f8353","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","Feature:Entity Analytics","Team:Entity Analytics","8.16 candidate","v8.16.0"],"title":"[Entity Analytics] Asset Criticality soft delete","number":193591,"url":"#193591 Analytics] Asset Criticality soft delete (#193591)\n\n## Summary\r\n\r\nThis PR introduces a \"soft delete\" for Asset Criticality records.\r\nInstead of deleting the document, we now simply change the criticality\r\nfield to the value `\"deleted\"`.\r\nThis value is fully managed on Kibana and should not be exposed to the\r\nclient side.\r\n\r\n\r\n### How to test\r\n\r\n1. Add some host/user data\r\n2. Make sure to enable the `entityStoreEnabled` feature flag\r\n3. Assign asset criticality to a user/host.\r\n* You may need to enable Asset Criticality in Kibana Advanced Settings\r\n5. Verify the criticality has been assigned by `GET .asset-citicality*`.\r\n6. Unassign the criticality for that host/user via the UI.\r\n7. `GET`ing the criticality index should now still show the updated\r\nrecord with `\"deleted\"` criticality value\r\n8. The Ui should also show criticality as `Unassigned` for the deleted\r\nrecord.\r\n\r\n\r\n\r\nImplements elastic/security-team#10531, which\r\nis part of the overall [Entity Store for\r\n8.16](elastic/security-team#10529) work","sha":"a8c7e0659635994546874fb1f7ec1304fa4f8353"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"#193591 Analytics] Asset Criticality soft delete (#193591)\n\n## Summary\r\n\r\nThis PR introduces a \"soft delete\" for Asset Criticality records.\r\nInstead of deleting the document, we now simply change the criticality\r\nfield to the value `\"deleted\"`.\r\nThis value is fully managed on Kibana and should not be exposed to the\r\nclient side.\r\n\r\n\r\n### How to test\r\n\r\n1. Add some host/user data\r\n2. Make sure to enable the `entityStoreEnabled` feature flag\r\n3. Assign asset criticality to a user/host.\r\n* You may need to enable Asset Criticality in Kibana Advanced Settings\r\n5. Verify the criticality has been assigned by `GET .asset-citicality*`.\r\n6. Unassign the criticality for that host/user via the UI.\r\n7. `GET`ing the criticality index should now still show the updated\r\nrecord with `\"deleted\"` criticality value\r\n8. The Ui should also show criticality as `Unassigned` for the deleted\r\nrecord.\r\n\r\n\r\n\r\nImplements elastic/security-team#10531, which\r\nis part of the overall [Entity Store for\r\n8.16](elastic/security-team#10529) work","sha":"a8c7e0659635994546874fb1f7ec1304fa4f8353"}},{"branch":"8.x","label":"v8.16.0","branchLabelMappingKey":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tiago Vila Verde <tiago.vilaverde@elastic.co>
- Loading branch information