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
# Backport This will backport the following commits from `main` to `8.10`: - [[Fleet] Fix security solution tag id (#164582)](#164582) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Cristina Amico","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-08-24T07:20:13Z","message":"[Fleet] Fix security solution tag id (#164582)\n\nRelated to https://github.com/elastic/kibana/issues/152814\r\n\r\n## Summary\r\n\r\nFix for a bug found in #162643 :\r\nThe security solution tag is actually created with \"Security Solution\"\r\nname and \"security-solution-default\" id (instead of `SecuritySolution`):\r\n\r\n```\r\n {\r\n \"id\": \"security-solution-default\",\r\n \"name\": \"Security Solution\",\r\n \"description\": \"\",\r\n \"color\": \"#D36086\"\r\n }\r\n```\r\n\r\nI found that in same cases the tag is duplicated, since[ is not created\r\nwith an unique\r\nid](https://github.com/elastic/kibana/blob/dd0938bea3ebd745a49ac164a7a5f053ba6a138b/x-pack/plugins/security_solution/public/dashboards/containers/use_fetch_security_tags.ts#L44-L51):\r\n\r\n<img width=\"3079\" alt=\"Screenshot 2023-08-23 at 15 07 09\"\r\nsrc=\"https://github.com/elastic/kibana/assets/16084106/ef885d8f-2e68-4695-aa14-1adc2e326ab0\">\r\n\r\nI think it's acceptable to use the \"security-solution-default\", at least\r\nit will create the correct tag name.\r\n\r\n### Test\r\nFor testing I used a package built locally that uses the `Security\r\nSolution` tag\r\nThe steps are the same as described in\r\nhttps://github.com//pull/162643\r\n\r\n- Additionally, check that the `tags` endpoint in the Tags page has name\r\nand id as described above:\r\n<img width=\"2521\" alt=\"Screenshot 2023-08-23 at 14 55 05\"\r\nsrc=\"https://github.com/elastic/kibana/assets/16084106/48b3ddd0-3d04-4ff6-8a24-946902687b13\">","sha":"da8d3b25c91deaba383a6d6a40d00522f7c6f463","branchLabelMapping":{"^v8.11.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v8.11.0"],"number":164582,"url":"https://github.com/elastic/kibana/pull/164582","mergeCommit":{"message":"[Fleet] Fix security solution tag id (#164582)\n\nRelated to https://github.com/elastic/kibana/issues/152814\r\n\r\n## Summary\r\n\r\nFix for a bug found in #162643 :\r\nThe security solution tag is actually created with \"Security Solution\"\r\nname and \"security-solution-default\" id (instead of `SecuritySolution`):\r\n\r\n```\r\n {\r\n \"id\": \"security-solution-default\",\r\n \"name\": \"Security Solution\",\r\n \"description\": \"\",\r\n \"color\": \"#D36086\"\r\n }\r\n```\r\n\r\nI found that in same cases the tag is duplicated, since[ is not created\r\nwith an unique\r\nid](https://github.com/elastic/kibana/blob/dd0938bea3ebd745a49ac164a7a5f053ba6a138b/x-pack/plugins/security_solution/public/dashboards/containers/use_fetch_security_tags.ts#L44-L51):\r\n\r\n<img width=\"3079\" alt=\"Screenshot 2023-08-23 at 15 07 09\"\r\nsrc=\"https://github.com/elastic/kibana/assets/16084106/ef885d8f-2e68-4695-aa14-1adc2e326ab0\">\r\n\r\nI think it's acceptable to use the \"security-solution-default\", at least\r\nit will create the correct tag name.\r\n\r\n### Test\r\nFor testing I used a package built locally that uses the `Security\r\nSolution` tag\r\nThe steps are the same as described in\r\nhttps://github.com//pull/162643\r\n\r\n- Additionally, check that the `tags` endpoint in the Tags page has name\r\nand id as described above:\r\n<img width=\"2521\" alt=\"Screenshot 2023-08-23 at 14 55 05\"\r\nsrc=\"https://github.com/elastic/kibana/assets/16084106/48b3ddd0-3d04-4ff6-8a24-946902687b13\">","sha":"da8d3b25c91deaba383a6d6a40d00522f7c6f463"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.11.0","labelRegex":"^v8.11.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/164582","number":164582,"mergeCommit":{"message":"[Fleet] Fix security solution tag id (#164582)\n\nRelated to https://github.com/elastic/kibana/issues/152814\r\n\r\n## Summary\r\n\r\nFix for a bug found in #162643 :\r\nThe security solution tag is actually created with \"Security Solution\"\r\nname and \"security-solution-default\" id (instead of `SecuritySolution`):\r\n\r\n```\r\n {\r\n \"id\": \"security-solution-default\",\r\n \"name\": \"Security Solution\",\r\n \"description\": \"\",\r\n \"color\": \"#D36086\"\r\n }\r\n```\r\n\r\nI found that in same cases the tag is duplicated, since[ is not created\r\nwith an unique\r\nid](https://github.com/elastic/kibana/blob/dd0938bea3ebd745a49ac164a7a5f053ba6a138b/x-pack/plugins/security_solution/public/dashboards/containers/use_fetch_security_tags.ts#L44-L51):\r\n\r\n<img width=\"3079\" alt=\"Screenshot 2023-08-23 at 15 07 09\"\r\nsrc=\"https://github.com/elastic/kibana/assets/16084106/ef885d8f-2e68-4695-aa14-1adc2e326ab0\">\r\n\r\nI think it's acceptable to use the \"security-solution-default\", at least\r\nit will create the correct tag name.\r\n\r\n### Test\r\nFor testing I used a package built locally that uses the `Security\r\nSolution` tag\r\nThe steps are the same as described in\r\nhttps://github.com//pull/162643\r\n\r\n- Additionally, check that the `tags` endpoint in the Tags page has name\r\nand id as described above:\r\n<img width=\"2521\" alt=\"Screenshot 2023-08-23 at 14 55 05\"\r\nsrc=\"https://github.com/elastic/kibana/assets/16084106/48b3ddd0-3d04-4ff6-8a24-946902687b13\">","sha":"da8d3b25c91deaba383a6d6a40d00522f7c6f463"}}]}] BACKPORT--> Co-authored-by: Cristina Amico <[email protected]>
- Loading branch information