Repository navigation
[aws] Update inspector data stream for Cloud Detection and Response (CDR) workflow #14306
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
Changes from 1 commit
9ff387c
bbd4c37
671472d
34a8fd6
b9b2494
729c0ce
75cb248
34fca8d
91bc1d0
29880df
70439b2
31c5699
4c117c1
ec76fc1
740956b
66c196a
c2747fc
79e53bf
b888df3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,6 +13,9 @@ | |
| - description: Enable request trace log removal. | ||
| type: enhancement | ||
| link: https://github.com/elastic/integrations/pull/14306 | ||
| - description: Update the kibana constraint to support ^8.19.0 || ^9.1.0 | ||
| type: enhancement | ||
| link: https://github.com/elastic/integrations/pull/14306 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think this is needed, and as it exists is misleading. The text here says (suggests?) that we are adding support for 8.19.0 and 9.1.0, but this is not what we are doing, we are restricting to these. I would instead suggest that this be removed since the behaviour is already implicitly documented by the integrations addition page for users who care about this. |
||
| - description: Remove metadata fields added by the Agentless policy. | ||
| type: bugfix | ||
| link: https://github.com/elastic/integrations/pull/14306 | ||
|
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @maxcold, current kibana version constraint is following: kibana:
version: "~8.16.6 || ~8.17.4 || ^8.18.0 || ^9.0.0"In Inspector, we don't have missing CVE values for package vulnerabilities. Also, it is not an array and always contain single values. For example: Do we still need to bump the minimum versions here? Related to multiple/empty CVEs: #14079 (comment)
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @kcreddy thanks for highlighting it! I need to test the integration with 8.18 and 9.0 to check that. Right now I'm testing with the latest 9.1 snapshot, will play with 8.18/9.0 version later
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. When testing 8.18 I realised that we don't support multiple packages in this version and also have some other rough edges. I think we will need to bump to
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. cc: @nick-alayil
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @brijesh-elastic, please update the versions to: cc: @maxcold |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -11,7 +11,7 @@ conditions: | |
| elastic: | ||
| subscription: basic | ||
| kibana: | ||
| version: "~8.16.6 || ~8.17.4 || ^8.18.0 || ^9.0.0" | ||
| version: "~8.16.6 || ~8.17.4 || ^8.19.0 || ^9.1.0" | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @brijesh-elastic @kcreddy as discussed this should be just
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. After another discussion, the version constraints and the transform changes will be part of another PR and merged close to |
||
| screenshots: | ||
| - src: /img/metricbeat-aws-overview.png | ||
| title: metricbeat aws overview | ||
|
|
||
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.
Why are we having same PR numbers and different descriptions ? Can't we combine these ?