-
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] [Advanced Settings] Hide settings that are not applicable to cu…
…rrent solution (#209136) (#211835) # Backport This will backport the following commits from `main` to `8.x`: - [[Advanced Settings] Hide settings that are not applicable to current solution (#209136)](#209136) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-19T19:20:06Z","message":"[Advanced Settings] Hide settings that are not applicable to current solution (#209136)\n\nCloses https://github.com/elastic/kibana/issues/196659\n\n## Summary\n\nThis PR adds a new setting schema field `solution` which is used in the\nAdvanced settings UI to decide whether to display the setting, depending\non the solution of the current space. If the `solution` is not set in\nthe setting definition, the setting will be displayed in all solutions.\nOtherwise, the setting will only be displayed in the set solution.\n\nThe current agreement is that we want to display all settings in the\n\"Observability\" settings category in the Oblt solution only and all\nsettings in the \"Security Solution\" settings category in the Security\nsolution only. Therefore, in this PR we set the `solution` field\naccordingly in the corresponding setting definitions. Note: We decided\nto add a new setting definition field `solution` rather than filtering\nby the already existing `category` field so that this approach works in\nthe future if we want to hide other single settings outside of these two\ncategories.\n\n**How to test:**\nVerify that in the classic solution, you can see all settings, and that\nthe solution-related settings mentioned above are only displayed in the\ncorresponding solution.\n\n\n\nhttps://github.com/user-attachments/assets/398ef3e6-973a-4283-ae20-229bf6139d60\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bc3fae5356c677c983138b26c7bc750266e42d1a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Kibana Management","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-security","Team:obs-ux-management","v9.1.0","v8.19.0"],"title":"[Advanced Settings] Hide settings that are not applicable to current solution","number":209136,"url":"https://github.com/elastic/kibana/pull/209136","mergeCommit":{"message":"[Advanced Settings] Hide settings that are not applicable to current solution (#209136)\n\nCloses https://github.com/elastic/kibana/issues/196659\n\n## Summary\n\nThis PR adds a new setting schema field `solution` which is used in the\nAdvanced settings UI to decide whether to display the setting, depending\non the solution of the current space. If the `solution` is not set in\nthe setting definition, the setting will be displayed in all solutions.\nOtherwise, the setting will only be displayed in the set solution.\n\nThe current agreement is that we want to display all settings in the\n\"Observability\" settings category in the Oblt solution only and all\nsettings in the \"Security Solution\" settings category in the Security\nsolution only. Therefore, in this PR we set the `solution` field\naccordingly in the corresponding setting definitions. Note: We decided\nto add a new setting definition field `solution` rather than filtering\nby the already existing `category` field so that this approach works in\nthe future if we want to hide other single settings outside of these two\ncategories.\n\n**How to test:**\nVerify that in the classic solution, you can see all settings, and that\nthe solution-related settings mentioned above are only displayed in the\ncorresponding solution.\n\n\n\nhttps://github.com/user-attachments/assets/398ef3e6-973a-4283-ae20-229bf6139d60\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bc3fae5356c677c983138b26c7bc750266e42d1a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209136","number":209136,"mergeCommit":{"message":"[Advanced Settings] Hide settings that are not applicable to current solution (#209136)\n\nCloses https://github.com/elastic/kibana/issues/196659\n\n## Summary\n\nThis PR adds a new setting schema field `solution` which is used in the\nAdvanced settings UI to decide whether to display the setting, depending\non the solution of the current space. If the `solution` is not set in\nthe setting definition, the setting will be displayed in all solutions.\nOtherwise, the setting will only be displayed in the set solution.\n\nThe current agreement is that we want to display all settings in the\n\"Observability\" settings category in the Oblt solution only and all\nsettings in the \"Security Solution\" settings category in the Security\nsolution only. Therefore, in this PR we set the `solution` field\naccordingly in the corresponding setting definitions. Note: We decided\nto add a new setting definition field `solution` rather than filtering\nby the already existing `category` field so that this approach works in\nthe future if we want to hide other single settings outside of these two\ncategories.\n\n**How to test:**\nVerify that in the classic solution, you can see all settings, and that\nthe solution-related settings mentioned above are only displayed in the\ncorresponding solution.\n\n\n\nhttps://github.com/user-attachments/assets/398ef3e6-973a-4283-ae20-229bf6139d60\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bc3fae5356c677c983138b26c7bc750266e42d1a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com>
- Loading branch information
1 parent
8c44d22
commit 7a729c7
Showing
22 changed files
with
210 additions
and
18 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
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.