elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.62k stars 8.22k forks source link

[Fleet]: User is not able edit existing agent policies, after running the Prefix namespace API. #193507

Open harshitgupta-qasource opened 1 month ago

harshitgupta-qasource commented 1 month ago

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 edit the agent policy and make any changes.
  8. Observe that User is not able save the changes to existing agent policies, after running the Prefix namespace API.

Expected Results

Screen-cast

https://github.com/user-attachments/assets/567f0ecc-904e-4494-b52c-305c883b21b4

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

elasticmachine commented 1 month ago

Pinging @elastic/fleet (Team:Fleet)

harshitgupta-qasource commented 1 month ago

@amolnater-qasource Kindly review

amolnater-qasource commented 1 month ago

Secondary review for this ticket is Done.

pra2107tham commented 1 month ago

Can I work on this issue @amolnater-qasource

jen-huang commented 1 month ago

@pra2107tham Thanks for your interest. This one is related to a core feature that is under heavy development ATM and is already planned for one of our team members to take a look at. I recommend picking up a different good first issue.