[eset_protect][imperva_cloud_waf][sentinal_one_cloud_funnel][ti_crowdstrike] Use modern ecs@mappings - #9778
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
|
|
Package eset_protect - 0.5.1 containing this change is available at https://epr.elastic.co/search?package=eset_protect |
|
Package imperva_cloud_waf - 0.3.1 containing this change is available at https://epr.elastic.co/search?package=imperva_cloud_waf |
|
Package sentinel_one_cloud_funnel - 0.14.2 containing this change is available at https://epr.elastic.co/search?package=sentinel_one_cloud_funnel |
|
Package ti_crowdstrike - 0.5.5 containing this change is available at https://epr.elastic.co/search?package=ti_crowdstrike |
|
@chrisberkhout For future reference, you probably want a shorter git commit summary line. The summary of this commit was truncated. https://kortschak.io/courses/git_workshop/communication/#commit-messages |
|
Should this release also have the kibana 8.13.0 requirement added on the download page? |
|
Hi @joshFive, The updated metadata will show up, for example here you'll see "Compatible Kibana version(s): 8.13.0 or higher". However, I noticed that all of these integrations had a hard-coded Kibana version number mentioned in the README. I've opened a PR to remove those so that the version constraints are in one place only, as we have it for many other integrations: #10182 |





Proposed commit message
Checklist
changelog.ymlfile.Related issues