-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Grouped features for role management #78152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3503921 to
34365ee
Compare
34365ee to
60d4f22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fixture is responsible for parsing the rendered component tree to extract the displayed privileges.
As a result of the refactoring here, dependent tests were updated to always expect a subFeaturePrivileges array in the response, whereas before it was optionally defined.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing dead code now that the spaces panels cannot be collapsed. Technically unrelated to this PR 😬
|
Pinging @elastic/kibana-security (Team:Security) |
|
ACK: will review today |
azasypkin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Tested locally all the scenarios I could think of and everything worked as expected.
| available; otherwise, it is not visible. | ||
|
|
||
| To apply your changes, click **Create space privilege**. The space privilege shows up under the Kibana privileges section of the role. | ||
| To apply your changes, click **Add Kibana privilege**. The space privilege shows up under the Kibana privileges section of the role. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: any reason you use {kib} in some places and hardcoded Kibana in others in this file? Also we still reference to privileges as space privileges in this document in some places, are these just leftovers or we want to explicitly say that these are Kibana privileges that are specific to some spaces?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope, just oversights! I will be overhauling these docs after FF, but I'll correct now and adjust after with fresh screenshots and the like
| background-color: $euiColorLightestShade; | ||
| padding-left: $euiSizeXXL; | ||
| padding-top: $euiSizeS; | ||
| } No newline at end of file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: missing new line at the EOF?
| } | |
| } | |
|
|
||
| if (feature2.reserved && !feature1.reserved) { | ||
| return -1; | ||
| const label: string = i18n.translate( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
optional nit: you could also use FormattedMessage react component. It's not a big deal, "theoretically" it's supposed to be more optimized for React, but I haven't seen any evidence yet, so up to you.
|
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Test FailuresX-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/execution_status·ts.alerting api integration spaces only Alerting executionStatus should eventually be "ok" for no-op alertStandard OutStack TraceMetrics [docs]async chunks size
page load bundle size
History
To update your PR or re-run it, just comment with: |
Groups features by category for Role Management
The role management screen has been updated to take advantage of the feature categories introduced in #74151. The old implementation displayed a flat table of features, and the ordering was not always predictable.
The updated interface organizes features according to the category in which they exist. Features can be configured independently as before. Unlike #74151, the categories for role management do not allow toggling privileges for entire categories. This was done to reduce confusion on an already complex form.
Out of scope
Relates: #72659
Resolves #54794
Resolves #74526