[Fleet] Fix namespaces property of created agent policies

[jillguyonnet]

Summary

I found a small bug while working on #185040: when agent policies are created, there should be a root-level namespaces property, which is currently missing.

GET .fleet-policies/_mapping contains a namespaces property with keyword type that was added in https://github.com/elastic/elasticsearch.

Note: I was looking into removing the existing data.namespaces property, however I don't see any issues with it. It is coming from here, i.e. the data property is generated from the full agent policy which already has a namespaces property.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[obltmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[nchaulet]

Thanks for fixing this 🚀

[jillguyonnet]

/ci

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: e512db1

Metrics [docs]

✅ unchanged

History

• 💔 Build #223971 failed 771fd30

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @jillguyonnet

[jillguyonnet]

@nchaulet Should this be backported to 8.15.0?

[nchaulet]

@nchaulet Should this be backported to 8.15.0?

I am not sure there is any value to backport it, it should not create any bugs with the feature flag disabled, and I do not think we expect to turn the flag on in 8.15.0