[Fleet] Added default index pattern creation to stream-based installation#199122
[Fleet] Added default index pattern creation to stream-based installation#199122xcrzx merged 1 commit intoelastic:mainfrom xcrzx:fix-default-index-patterns
Conversation
PhilippeOberti
left a comment
There was a problem hiding this comment.
Thanks for opening this PR. The change fixes our Threat Hunting Investigations Cypress tests that started failing right after this PR was merged
...test/security_solution_cypress/cypress/e2e/investigations/sourcerer/sourcerer_timeline.cy.ts
Outdated
Show resolved
Hide resolved
|
Pinging @elastic/fleet (Team:Fleet) |
PhilippeOberti
left a comment
There was a problem hiding this comment.
thanks for unskipping our test, left a super minor comment on removing the obsolete comment
...test/security_solution_cypress/cypress/e2e/investigations/sourcerer/sourcerer_timeline.cy.ts
Outdated
Show resolved
Hide resolved
PhilippeOberti
left a comment
There was a problem hiding this comment.
LGTM for the Threat Hunting Investigations team. Thanks for fixing this and unskipping our tests!!
💚 Build Succeeded
Metrics [docs]
History
cc @xcrzx |
|
Starting backport for target branches: 8.x |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…tion (elastic#199122) **Related to: elastic#195888 ## Summary Add default index pattern creation to the new stream-based package installation method to match the behavior of standard package installation. Switching to stream-based package installation resulted in the default index patterns not being created, even after installing the rules package. While this likely doesn’t affect production, as multiple integrations are usually installed in Kibana (creating the default index pattern in any case), this change has impacted some tests: elastic#199030. So restoring the original behaviour
…stallation (#199122) (#199453) # Backport This will backport the following commits from `main` to `8.x`: - [[Fleet] Added default index pattern creation to stream-based installation (#199122)](#199122) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2024-11-07T09:04:56Z","message":"[Fleet] Added default index pattern creation to stream-based installation (#199122)\n\n**Related to: https://github.com/elastic/kibana/pull/195888**\r\n\r\n## Summary\r\n\r\nAdd default index pattern creation to the new stream-based package\r\ninstallation method to match the behavior of standard package\r\ninstallation.\r\n\r\nSwitching to stream-based package installation resulted in the default\r\nindex patterns not being created, even after installing the rules\r\npackage. While this likely doesn’t affect production, as multiple\r\nintegrations are usually installed in Kibana (creating the default index\r\npattern in any case), this change has impacted some tests:\r\nhttps://github.com//pull/199030. So restoring the original\r\nbehaviour","sha":"22d3e628931706dee4c0d8eec068575d264bb13e","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:version","v8.17.0"],"number":199122,"url":"https://github.com/elastic/kibana/pull/199122","mergeCommit":{"message":"[Fleet] Added default index pattern creation to stream-based installation (#199122)\n\n**Related to: https://github.com/elastic/kibana/pull/195888**\r\n\r\n## Summary\r\n\r\nAdd default index pattern creation to the new stream-based package\r\ninstallation method to match the behavior of standard package\r\ninstallation.\r\n\r\nSwitching to stream-based package installation resulted in the default\r\nindex patterns not being created, even after installing the rules\r\npackage. While this likely doesn’t affect production, as multiple\r\nintegrations are usually installed in Kibana (creating the default index\r\npattern in any case), this change has impacted some tests:\r\nhttps://github.com//pull/199030. So restoring the original\r\nbehaviour","sha":"22d3e628931706dee4c0d8eec068575d264bb13e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199122","number":199122,"mergeCommit":{"message":"[Fleet] Added default index pattern creation to stream-based installation (#199122)\n\n**Related to: https://github.com/elastic/kibana/pull/195888**\r\n\r\n## Summary\r\n\r\nAdd default index pattern creation to the new stream-based package\r\ninstallation method to match the behavior of standard package\r\ninstallation.\r\n\r\nSwitching to stream-based package installation resulted in the default\r\nindex patterns not being created, even after installing the rules\r\npackage. While this likely doesn’t affect production, as multiple\r\nintegrations are usually installed in Kibana (creating the default index\r\npattern in any case), this change has impacted some tests:\r\nhttps://github.com//pull/199030. So restoring the original\r\nbehaviour","sha":"22d3e628931706dee4c0d8eec068575d264bb13e"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
Related to: #195888
Summary
Add default index pattern creation to the new stream-based package installation method to match the behavior of standard package installation.
Switching to stream-based package installation resulted in the default index patterns not being created, even after installing the rules package. While this likely doesn’t affect production, as multiple integrations are usually installed in Kibana (creating the default index pattern in any case), this change has impacted some tests: #199030. So restoring the original behaviour