Pass namespaces to Fleet Server managed documents

[nchaulet]

Description

Resolve #3505

Set the namespaces property in the different .fleet-* document managed by fleet server.

Feature flag? do we need to release that feature under a feature flag, in my opinion if the namespaces are not populated in Kibana fleet server behavior do not change so it should be safe to release this without feature flag.

Test

I added a new integration test to cover the change

Todo

• Pass namespace during enrollments
• Pass namespace for actions
• Pass namespace during file upload
• Add integrations test for namespace

Questions

• Policy change should we support changing namespace here ? @kpollich what do you think?

[kpollich]

Policy change should we support changing namespace here ? @kpollich what do you think?

We were initially planning to allow for changing an agent policy's space directly from Fleet UI, e.g.

However, it's not clear if this is the direction we'll go. We may direct users to stack management instead, to avoid having multiple sources of truth for object/space management. When the space of an agent policy changes, though, we probably do need to dispatch an action to update the namespaces property on its relevant policy components. I wonder if we could register a callback with stack management that detects when a policy is moved to another space so we can fire off the policy change operation. We might be able to also handle this in a background task that listens for a certain saved object save event - if that's a thing.

[michel-laterman]

Looks good so far.
It's good that namespace is kept as an ES document detail and not added to the API that clients use.

Please add a changelog fragment as well

[nchaulet]

We were initially planning to allow for changing an agent policy's space directly from Fleet UI, e.g.

I think we probably can handle the whole namespace change directly from Kibana has we do when reassigning to a policy by updating the .fleet-agents doc

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
90.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube