-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EDR Workflows] Fix invalid event filter for cloud workloads #208974
[EDR Workflows] Fix invalid event filter for cloud workloads #208974
Conversation
Pinging @elastic/security-defend-workflows (Team:Defend Workflows) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@@ -7,7 +7,7 @@ | |||
|
|||
import * as t from 'io-ts'; | |||
|
|||
export const meta = t.object; | |||
export const meta = t.UnknownRecord; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome. Thanks for digging into it and ensuring the type is properly defined.
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
Unknown metric groupsReferences to deprecated APIs
History
|
Starting backport for target branches: 8.16, 8.17, 8.18, 8.x, 9.0 https://github.com/elastic/kibana/actions/runs/13114342150 |
…#208974) ## Summary Fixes the bug of the invalid event filter created automatically when creating a cloud workloads endpoint integration. The issue was a type issue: `undefined` or an object is expected, instead an array was passed. To make sure this does not happen again, the type for the `meta` field was updated from the deprecated `t.object` to `t.UnknownRecord`, which is able to catch similar issues as a type error: ca0c01b ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 158a077)
…#208974) ## Summary Fixes the bug of the invalid event filter created automatically when creating a cloud workloads endpoint integration. The issue was a type issue: `undefined` or an object is expected, instead an array was passed. To make sure this does not happen again, the type for the `meta` field was updated from the deprecated `t.object` to `t.UnknownRecord`, which is able to catch similar issues as a type error: ca0c01b ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 158a077)
…#208974) ## Summary Fixes the bug of the invalid event filter created automatically when creating a cloud workloads endpoint integration. The issue was a type issue: `undefined` or an object is expected, instead an array was passed. To make sure this does not happen again, the type for the `meta` field was updated from the deprecated `t.object` to `t.UnknownRecord`, which is able to catch similar issues as a type error: ca0c01b ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 158a077)
…#208974) ## Summary Fixes the bug of the invalid event filter created automatically when creating a cloud workloads endpoint integration. The issue was a type issue: `undefined` or an object is expected, instead an array was passed. To make sure this does not happen again, the type for the `meta` field was updated from the deprecated `t.object` to `t.UnknownRecord`, which is able to catch similar issues as a type error: ca0c01b ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 158a077)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. 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 |
…#208974) ## Summary Fixes the bug of the invalid event filter created automatically when creating a cloud workloads endpoint integration. The issue was a type issue: `undefined` or an object is expected, instead an array was passed. To make sure this does not happen again, the type for the `meta` field was updated from the deprecated `t.object` to `t.UnknownRecord`, which is able to catch similar issues as a type error: ca0c01b ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit 158a077) # Conflicts: # x-pack/plugins/security_solution/server/fleet_integration/fleet_integration.test.ts
…208974) (#209288) # Backport This will backport the following commits from `main` to `8.x`: - [[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)](#208974) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T13:15:17Z","message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Fix invalid event filter for cloud workloads","number":208974,"url":"https://github.com/elastic/kibana/pull/208974","mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208974","number":208974,"mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>
…208974) (#209284) # Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)](#208974) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T13:15:17Z","message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Fix invalid event filter for cloud workloads","number":208974,"url":"https://github.com/elastic/kibana/pull/208974","mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208974","number":208974,"mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>
…208974) (#209285) # Backport This will backport the following commits from `main` to `8.18`: - [[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)](#208974) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T13:15:17Z","message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Fix invalid event filter for cloud workloads","number":208974,"url":"https://github.com/elastic/kibana/pull/208974","mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208974","number":208974,"mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>
…208974) (#209290) # Backport This will backport the following commits from `main` to `9.0`: - [[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)](#208974) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T13:15:17Z","message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Fix invalid event filter for cloud workloads","number":208974,"url":"https://github.com/elastic/kibana/pull/208974","mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208974","number":208974,"mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}}]}] BACKPORT--> Co-authored-by: Gergő Ábrahám <gergo.abraham@elastic.co>
…208974) (#209330) # Backport This will backport the following commits from `main` to `8.16`: - [[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)](#208974) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gergő Ábrahám","email":"gergo.abraham@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T13:15:17Z","message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[EDR Workflows] Fix invalid event filter for cloud workloads","number":208974,"url":"https://github.com/elastic/kibana/pull/208974","mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208974","number":208974,"mergeCommit":{"message":"[EDR Workflows] Fix invalid event filter for cloud workloads (#208974)\n\n## Summary\r\n\r\nFixes the bug of the invalid event filter created automatically when\r\ncreating a cloud workloads endpoint integration. The issue was a type\r\nissue: `undefined` or an object is expected, instead an array was\r\npassed.\r\n\r\nTo make sure this does not happen again, the type for the `meta` field\r\nwas updated from the deprecated `t.object` to `t.UnknownRecord`, which\r\nis able to catch similar issues as a type error:\r\nca0c01b63beb40fb19188deae2257d89d8b3ba90\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\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\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"158a0777319175b64311c3344dc5cf12e1e6ccc7"}},{"url":"https://github.com/elastic/kibana/pull/209284","number":209284,"branch":"8.17","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/209285","number":209285,"branch":"8.18","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/209288","number":209288,"branch":"8.x","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/209290","number":209290,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
Fixes the bug of the invalid event filter created automatically when creating a cloud workloads endpoint integration. The issue was a type issue:
undefined
or an object is expected, instead an array was passed.To make sure this does not happen again, the type for the
meta
field was updated from the deprecatedt.object
tot.UnknownRecord
, which is able to catch similar issues as a type error: ca0c01bChecklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.