-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [UII] Fix first time integration flow when using multiple spaces (
#194350) (#194882) # Backport This will backport the following commits from `main` to `8.x`: - [[UII] Fix first time integration flow when using multiple spaces (#194350)](#194350) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-10-03T23:07:04Z","message":"[UII] Fix first time integration flow when using multiple spaces (#194350)\n\n## Summary\r\n\r\nResolves #182736. This PR fixes the first time Elastic Agent user\r\nonboarding flow (only shown on Cloud) by prefixing the user's current\r\nspace ID to the default agent policy that is created behind the scenes\r\nif the user has opted into using Fleet's space awareness.\r\n\r\nThis makes it so that Fleet correctly identifies whether there are any\r\nagents enrolled in the current space, and directs the user to the\r\nmulti-step onboarding flow for adding integrations if there are no\r\nagents enrolled in the current space's scoped agent policies.\r\n\r\nAn example policy ID created this way may look like\r\n`second-space:fleet-first-agent-policy`. If the current space is the\r\n`default` space, the ID remains as `fleet-first-agent-policy`.\r\n\r\nDue to prefixing using a `:`, I also had to put policy ID in quotes\r\nwhere ever it appears in kueries for filtering, i.e. `policy_id:\"<some\r\nid>\"`. This change comprises most of the changed files in this PR.","sha":"6f213cfb1cf548785271b89dd8199e13d09fd578","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","ci:cloud-deploy"],"title":"[UII] Fix first time integration flow when using multiple spaces","number":194350,"url":"https://github.com/elastic/kibana/pull/194350","mergeCommit":{"message":"[UII] Fix first time integration flow when using multiple spaces (#194350)\n\n## Summary\r\n\r\nResolves #182736. This PR fixes the first time Elastic Agent user\r\nonboarding flow (only shown on Cloud) by prefixing the user's current\r\nspace ID to the default agent policy that is created behind the scenes\r\nif the user has opted into using Fleet's space awareness.\r\n\r\nThis makes it so that Fleet correctly identifies whether there are any\r\nagents enrolled in the current space, and directs the user to the\r\nmulti-step onboarding flow for adding integrations if there are no\r\nagents enrolled in the current space's scoped agent policies.\r\n\r\nAn example policy ID created this way may look like\r\n`second-space:fleet-first-agent-policy`. If the current space is the\r\n`default` space, the ID remains as `fleet-first-agent-policy`.\r\n\r\nDue to prefixing using a `:`, I also had to put policy ID in quotes\r\nwhere ever it appears in kueries for filtering, i.e. `policy_id:\"<some\r\nid>\"`. This change comprises most of the changed files in this PR.","sha":"6f213cfb1cf548785271b89dd8199e13d09fd578"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/194350","number":194350,"mergeCommit":{"message":"[UII] Fix first time integration flow when using multiple spaces (#194350)\n\n## Summary\r\n\r\nResolves #182736. This PR fixes the first time Elastic Agent user\r\nonboarding flow (only shown on Cloud) by prefixing the user's current\r\nspace ID to the default agent policy that is created behind the scenes\r\nif the user has opted into using Fleet's space awareness.\r\n\r\nThis makes it so that Fleet correctly identifies whether there are any\r\nagents enrolled in the current space, and directs the user to the\r\nmulti-step onboarding flow for adding integrations if there are no\r\nagents enrolled in the current space's scoped agent policies.\r\n\r\nAn example policy ID created this way may look like\r\n`second-space:fleet-first-agent-policy`. If the current space is the\r\n`default` space, the ID remains as `fleet-first-agent-policy`.\r\n\r\nDue to prefixing using a `:`, I also had to put policy ID in quotes\r\nwhere ever it appears in kueries for filtering, i.e. `policy_id:\"<some\r\nid>\"`. This change comprises most of the changed files in this PR.","sha":"6f213cfb1cf548785271b89dd8199e13d09fd578"}}]}] BACKPORT--> Co-authored-by: Jen Huang <[email protected]>
- Loading branch information
1 parent
edde4bd
commit ece07e0
Showing
10 changed files
with
76 additions
and
53 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters