wiz: fix missing score handling and retain cloud_configuration_rule_description #11489
Conversation
efd6
added
enhancement
| - version: "1.8.2" | ||
| changes: | ||
| - description: Relax requirement for vulnerability score to be present. | ||
| type: bugfix | ||
| link: https://github.com/elastic/integrations/pull/11489 | ||
| - description: Retain `cloudConfigurationRuleDescription` from `sourceRule`. | ||
| type: enhancement | ||
| link: https://github.com/elastic/integrations/pull/11489 |
There was a problem hiding this comment.
This is unfortunately required to be a patch bump despite being an enhancement due to constraints that exist due to the use of preview marks in the 1.9 version of the integration published in main.
There was a problem hiding this comment.
Thanks for the clarification.
| - name: cloud_configuration_rule_description | ||
| type: keyword |
There was a problem hiding this comment.
This should really be a match_only_text, but the other fields here, control_description and resolution_recommendation should also, so maintaining alignment and not breaking things by fixing those fields.
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
History
cc @efd6 |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
Package wiz - 1.8.2 containing this change is available at https://epr.elastic.co/search?package=wiz |
Proposed commit message
See title.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots