mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
4d53520eea
# Backport This will backport the following commits from `main` to `8.x`: - [initial @kbn/scout-security plugin (#210433)](https://github.com/elastic/kibana/pull/210433) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gloria Hornero","email":"gloria.hornero@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T10:59:30Z","message":"initial @kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are adding the initial structure for the\n@kibana/scout-security package, note that this is not ready to be used\nand any new test using this package, is not going to be executed as part\nof the regular pipelines, meaning, you are not going to add coverage to\nthe application. \n\n@kibana/scout-security package is a test package that extends @kbn/scout\nwith test helpers specifically designed to test Security Solution\nfunctionalities in Kibana. All tests under Security plugins should only\nimport from @kbn/scout-security, not from @kbn/scout. \n\nThis PR is a POC to start testing development by providing custom\nPlaywright fixtures, page objects, and utilities tailored for\nSecurity-related testing scenarios.\n\nThings to follow-up: \n\n- CustomQueryRule interface is already declared in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas `QueryRuleCreateProps` \n- DETECTION_ENGINE_RULES_URL and DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in `@kbn/security-solution-plugin/common/constants`\n\nIt would be great if all of that is extracted from the plugin to a\npackage so it can be reused instead of having to duplicate the code.\n\nUntil the package is not ready to be used and has not been introduced to\nthe different teams, appex-qa and myself will be the owners of it to\nmake sure that best practices are followed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","backport:version","Team: Sec Eng Productivity","test:scout","v9.1.0","v8.19.0"],"title":"initial @kbn/scout-security plugin","number":210433,"url":"https://github.com/elastic/kibana/pull/210433","mergeCommit":{"message":"initial @kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are adding the initial structure for the\n@kibana/scout-security package, note that this is not ready to be used\nand any new test using this package, is not going to be executed as part\nof the regular pipelines, meaning, you are not going to add coverage to\nthe application. \n\n@kibana/scout-security package is a test package that extends @kbn/scout\nwith test helpers specifically designed to test Security Solution\nfunctionalities in Kibana. All tests under Security plugins should only\nimport from @kbn/scout-security, not from @kbn/scout. \n\nThis PR is a POC to start testing development by providing custom\nPlaywright fixtures, page objects, and utilities tailored for\nSecurity-related testing scenarios.\n\nThings to follow-up: \n\n- CustomQueryRule interface is already declared in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas `QueryRuleCreateProps` \n- DETECTION_ENGINE_RULES_URL and DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in `@kbn/security-solution-plugin/common/constants`\n\nIt would be great if all of that is extracted from the plugin to a\npackage so it can be reused instead of having to duplicate the code.\n\nUntil the package is not ready to be used and has not been introduced to\nthe different teams, appex-qa and myself will be the owners of it to\nmake sure that best practices are followed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210433","number":210433,"mergeCommit":{"message":"initial @kbn/scout-security plugin (#210433)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/210298\n\nIn this PR we are adding the initial structure for the\n@kibana/scout-security package, note that this is not ready to be used\nand any new test using this package, is not going to be executed as part\nof the regular pipelines, meaning, you are not going to add coverage to\nthe application. \n\n@kibana/scout-security package is a test package that extends @kbn/scout\nwith test helpers specifically designed to test Security Solution\nfunctionalities in Kibana. All tests under Security plugins should only\nimport from @kbn/scout-security, not from @kbn/scout. \n\nThis PR is a POC to start testing development by providing custom\nPlaywright fixtures, page objects, and utilities tailored for\nSecurity-related testing scenarios.\n\nThings to follow-up: \n\n- CustomQueryRule interface is already declared in\n`x-pack/solutions/security/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_schemas.gen.ts`\nas `QueryRuleCreateProps` \n- DETECTION_ENGINE_RULES_URL and DETECTION_ENGINE_RULES_BULK_ACTION are\nalready declared in `@kbn/security-solution-plugin/common/constants`\n\nIt would be great if all of that is extracted from the plugin to a\npackage so it can be reused instead of having to duplicate the code.\n\nUntil the package is not ready to be used and has not been introduced to\nthe different teams, appex-qa and myself will be the owners of it to\nmake sure that best practices are followed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>","sha":"d5a0501fb8148b4274a00921a6061d850b142f28"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
|---|---|---|
| .. | ||
| codeql | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| ISSUE_TEMPLATE.md | ||
| paths-labeller.yml | ||
| PULL_REQUEST_TEMPLATE.md | ||
| relabel.yml | ||
| stale.yml | ||