Adapt definitions of nested subfields to current Fleet implementation - #11016
Conversation
jsoriano
added
Integration:gcp
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
cc @jsoriano |
|
efd6
left a comment
efd6
left a comment
There was a problem hiding this comment.
Checked akamai. Looks good.
|
@lalit-satapathy @axw could we please get someone from your team reviewing this? |
ishleenk17
left a comment
ishleenk17
left a comment
There was a problem hiding this comment.
Reviewed gcp package from infraobs team. Looks good!
|
I only looked at gcp, and mostly rubberstamping because @ishleenk17 already looked. (Logic looks sound though.) |
|
Package akamai - 2.25.1 containing this change is available at https://epr.elastic.co/search?package=akamai |
|
Package falco - 0.1.1 containing this change is available at https://epr.elastic.co/search?package=falco |
|
Package gcp - 2.37.2 containing this change is available at https://epr.elastic.co/search?package=gcp |
|
Package github - 1.29.1 containing this change is available at https://epr.elastic.co/search?package=github |
|
Package google_workspace - 2.25.1 containing this change is available at https://epr.elastic.co/search?package=google_workspace |
|
Package jamf_protect - 2.6.1 containing this change is available at https://epr.elastic.co/search?package=jamf_protect |
|
Package tanium - 1.10.1 containing this change is available at https://epr.elastic.co/search?package=tanium |
|
Package trellix_edr_cloud - 1.2.1 containing this change is available at https://epr.elastic.co/search?package=trellix_edr_cloud |
…elastic#11016) These mappings were correctly defined as expected by the spec, but Fleet was only installing empty nested objects. To workaround that, subfields can be moved to have their own definitions. Issue in Fleet is fixed in elastic/kibana#191730, we can apply this workaround for current versions of the stack.
…elastic#11016) These mappings were correctly defined as expected by the spec, but Fleet was only installing empty nested objects. To workaround that, subfields can be moved to have their own definitions. Issue in Fleet is fixed in elastic/kibana#191730, we can apply this workaround for current versions of the stack.
6 participants
Proposed commit message
Adapt definitions of subfields of nested objects so they are actually installed by Fleet. New mappings are otherwise equivalent.
These mappings were correctly defined as expected by the spec, but Fleet was only installing empty nested objects. To workaround that, subfields can be moved to have their own definitions.
Issue in Fleet is fixed in elastic/kibana#191730, but we can apply this workaround for older versions of the stack.
Checklist
changelog.ymlfile.How to test this PR locally
Install one of these packages, and check that the index templates include the mappings for the fields of the nested objects.
Related issues