Add 24h period configuration to all CSPM providers - #8516
Conversation
oren-zohar
left a comment
There was a problem hiding this comment.
Can you please verify these changes locally?
🌐 Coverage report
|
74a5cde to
28143ea
Compare
|
Package cloud_security_posture - 1.7.0-preview03 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
|
Package cloud_security_posture - 1.7.0-preview04 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
|
Package cloud_security_posture - 1.7.0-preview05 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
|
Package cloud_security_posture - 1.7.0-preview06 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
|
Package cloud_security_posture - 1.7.0-preview07 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
|
Package cloud_security_posture - 1.7.0-preview08 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
|
Package cloud_security_posture - 1.7.0-preview09 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
|
Package cloud_security_posture - 1.7.0 containing this change is available at https://epr.elastic.co/search?package=cloud_security_posture |
This reverts commit eee96ef.
This reverts commit 0351c96.
Why
As mentioned on elastic/cloudbeat#1478 currently only CSPM AWS runs on a 24h cycle, GCP and Azure run on a 4h cycle (default value), while all CSPM should run on a 24h period.
What
Add 24h period configuration to all CSPMs. AWS already had, added to GCP and Azure.
Checklist
changelog.ymlfile.Author's Checklist
Related issues