-
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] [Synthetics] Sub-feature for managing private locations !! (#20…
…1100) (#202496) # Backport This will backport the following commits from `main` to `8.x`: - [[Synthetics] Sub-feature for managing private locations !! (#201100)](#201100) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-12-02T14:53:26Z","message":"[Synthetics] Sub-feature for managing private locations !! (#201100)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/200899\r\n\r\nAdded Synthetics Sub-feature for managing private locations !!\r\n\r\nUser can configure a sub feature in a role under synthetics to allow\r\nmanaging private locations ,\r\n\r\nwith role API it will be with \r\n```\r\n{\r\n kibana: [\r\n {\r\n feature: {\r\n uptime: [\r\n 'minimal_all',\r\n 'can_manage_private_locations',\r\n ],\r\n },\r\n spaces: ['*'],\r\n },\r\n ],\r\n }\r\n```\r\n\r\n\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f842da22-9c82-43d0-ad34-c6e19ea187c6\">\r\n\r\nCreate/delete actions on UI will be disabled \r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1a164d85-357b-42f3-ae15-0682b2db6c75\">\r\n\r\n## Release note\r\nIf you have already modified sub feature for the synthetics/uptime\r\nfeature to disable user access for using elastic managed location,\r\naddition of this feature means, they will also will not be able to\r\nmanage(add/delete) private locations. Though this will not impact usage\r\nof private locations in monitors. If you want those users to have\r\nability to add/delete new private locations, you can enable that by\r\ntoggle this feature in role ui or via api.","sha":"93eedff53c8b9c3ebe55dfdb71029336c03542f0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:breaking","v9.0.0","release_note:feature","ci:project-deploy-observability","Team:obs-ux-management","backport:version","v8.18.0"],"title":"[Synthetics] Sub-feature for managing private locations !!","number":201100,"url":"https://github.com/elastic/kibana/pull/201100","mergeCommit":{"message":"[Synthetics] Sub-feature for managing private locations !! (#201100)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/200899\r\n\r\nAdded Synthetics Sub-feature for managing private locations !!\r\n\r\nUser can configure a sub feature in a role under synthetics to allow\r\nmanaging private locations ,\r\n\r\nwith role API it will be with \r\n```\r\n{\r\n kibana: [\r\n {\r\n feature: {\r\n uptime: [\r\n 'minimal_all',\r\n 'can_manage_private_locations',\r\n ],\r\n },\r\n spaces: ['*'],\r\n },\r\n ],\r\n }\r\n```\r\n\r\n\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f842da22-9c82-43d0-ad34-c6e19ea187c6\">\r\n\r\nCreate/delete actions on UI will be disabled \r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1a164d85-357b-42f3-ae15-0682b2db6c75\">\r\n\r\n## Release note\r\nIf you have already modified sub feature for the synthetics/uptime\r\nfeature to disable user access for using elastic managed location,\r\naddition of this feature means, they will also will not be able to\r\nmanage(add/delete) private locations. Though this will not impact usage\r\nof private locations in monitors. If you want those users to have\r\nability to add/delete new private locations, you can enable that by\r\ntoggle this feature in role ui or via api.","sha":"93eedff53c8b9c3ebe55dfdb71029336c03542f0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201100","number":201100,"mergeCommit":{"message":"[Synthetics] Sub-feature for managing private locations !! (#201100)\n\n## Summary\r\n\r\nFixes https://github.com/elastic/kibana/issues/200899\r\n\r\nAdded Synthetics Sub-feature for managing private locations !!\r\n\r\nUser can configure a sub feature in a role under synthetics to allow\r\nmanaging private locations ,\r\n\r\nwith role API it will be with \r\n```\r\n{\r\n kibana: [\r\n {\r\n feature: {\r\n uptime: [\r\n 'minimal_all',\r\n 'can_manage_private_locations',\r\n ],\r\n },\r\n spaces: ['*'],\r\n },\r\n ],\r\n }\r\n```\r\n\r\n\r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/f842da22-9c82-43d0-ad34-c6e19ea187c6\">\r\n\r\nCreate/delete actions on UI will be disabled \r\n\r\n<img width=\"1728\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/1a164d85-357b-42f3-ae15-0682b2db6c75\">\r\n\r\n## Release note\r\nIf you have already modified sub feature for the synthetics/uptime\r\nfeature to disable user access for using elastic managed location,\r\naddition of this feature means, they will also will not be able to\r\nmanage(add/delete) private locations. Though this will not impact usage\r\nof private locations in monitors. If you want those users to have\r\nability to add/delete new private locations, you can enable that by\r\ntoggle this feature in role ui or via api.","sha":"93eedff53c8b9c3ebe55dfdb71029336c03542f0"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Shahzad <[email protected]>
- Loading branch information
1 parent
bef94d0
commit d04aa2a
Showing
24 changed files
with
307 additions
and
151 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
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
Oops, something went wrong.