[Fleet]: Integration added to agent policy in new space not visible under default space policy.

[harshitgupta-qasource]

Kibana Build details:

VERSION: 8.16.0 SNAPSHOT
BUILD: 78344
COMMIT: ec719e0c2adbf707701892198743dd7b263a5b67

Preconditions:

1. 8.16.0 or above Kibana should be available.
2. Agent Policy should be created.
3. Two or more space should be created.
4. Few polices should be added to secondary space.

Steps to reproduce:

1. Log into the Default Space.
2. Navigate to Stack Management > Dev Console.
3. Run the Command:

   PUT kbn:/s/{space1}/api/fleet/space_settings
   {
   "allowed_namespace_prefixes": ["space1"]
   } 

4. Observe that Kibana Fleet API accepts Namespace Prefix for Second space.
5. Now, Login into Space1.
6. Navigate to Fleet > Agent Policies Tab.
7. Click on any agent policy (policy should be allocated to both new space and Default Space) and add any integration.
8. Observe that User is able to add integration to agent policy on new space.
9. Now, Login into Default Space.
10. Navigate to Fleet > Agent Policies Tab.
11. Open the same agent policy on which integration is added to new space.
12. Observe that Integration added to agent policy in new space not visible under default space policy.

Expected Results

• Integration added to agent policy in new space should be visible under default space policy..

Screen-cast

https://github.com/user-attachments/assets/959dbfb4-6021-4ea9-bac7-b4fe678aec26

Screen-shot

• Default Space

• Space 1

Agent Policies

• Default Space Default Space.zip

• Space 1 Space1.zip

Feature: https://github.com/elastic/ingest-dev/issues/1664

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[harshitgupta-qasource]

@amolnater-qasource Kindly review

[amolnater-qasource]

Secondary review on this ticket is Done!

[nchaulet]

Seems fixed by https://github.com/elastic/kibana/pull/197487