Toby Brain

Support both mapped and typed input schemas in Fleet integration polies

1

Related to https://github.com/elastic/terraform-provider-elasticstack/issues/601 Integration policies support two body formats, a map (`{"input-id": {...}}`) and a list (`[{"type":"endpoint"...}]`). Only the latter form supports the `config` field used by both Endpoint and...

There's a few generator related issues we're hoping to avoid with this task: * These nested types can be defined as anonymous structs in Go (see [this](https://github.com/elastic/terraform-provider-elasticstack/pull/1224#discussion_r2260237476) discussion). Whilst they're...

For example [this](https://github.com/elastic/terraform-provider-elasticstack/actions/runs/13732252019/job/38482105848?pr=1045) test run.