-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Prevent Spaces from being disabled #115283
Prevent Spaces from being disabled #115283
Conversation
* Change config * Remove related deprecations * Remove space-disabled elements from role management UI * Remove security_only functional tests
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.
Author's notes for reviewers.
After this merges, we'll probably need to rebalance the CI jobs since we're getting rid of so many integration tests 🎉
FooAllAtEverythingSpace, | ||
FooAllAtNothingSpace, | ||
FooReadAtEverythingSpace, | ||
FooReadAtNothingSpace, |
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.
I added these scenarios because tests with the FooAll
and FooRead
users were present in the security_only
test suite, but not in this security_and_spaces
test suite.
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.
🏅 Thanks for observing this and not just blindly deleting the other test suites. This was done intentionally back in the day in order to reduce unnecessary duplication between the test suites.
export const UserAtSpaceScenarios: [ | ||
NoKibanaPrivilegesAtEverythingSpace, | ||
NoKibanaPrivilegesAtNothingSpace, | ||
SuperuserAtEverythingSpace, | ||
SuperuserAtNothingSpace, | ||
LegacyAllAtEverythingSpace, | ||
LegacyAllAtNothingSpace, | ||
DualPrivilegesAllAtEverythingSpace, | ||
DualPrivilegesAllAtNothingSpace, | ||
DualPrivilegesReadAtEverythingSpace, | ||
DualPrivilegesReadAtNothingSpace, | ||
GlobalAllAtEverythingSpace, | ||
GlobalAllAtNothingSpace, | ||
GlobalReadAtEverythingSpace, | ||
GlobalReadAtNothingSpace, | ||
EverythingSpaceAllAtEverythingSpace, | ||
EverythingSpaceAllAtNothingSpace, | ||
EverythingSpaceReadAtEverythingSpace, | ||
EverythingSpaceReadAtNothingSpace, | ||
NothingSpaceAllAtEverythingSpace, | ||
NothingSpaceAllAtNothingSpace, | ||
NothingSpaceReadAtEverythingSpace, | ||
NothingSpaceReadAtNothingSpace | ||
] = [ | ||
export const UserAtSpaceScenarios = [ |
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.
We don't need to specify the type like this when we use as const
below 😉
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
To update your PR or re-run it, just comment with: |
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.
stack management changes lgtm 🚀
@elasticmachine merge upstream |
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! Still testing locally, but I don't expect any complications there
@@ -7,11 +7,6 @@ | |||
|
|||
By default, spaces is enabled in {kib}. To secure spaces, <<security-settings-kb,enable security>>. | |||
|
|||
`xpack.spaces.enabled`:: |
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.
I can't leave a comment on an unedited file, but we should update our docs to reflect the fact that we can't disable Spaces anymore. My preference is to keep the section, but change the wording to indicate that this is no longer possible as of 8.0. That said, I'll be ok if you'd rather remove this altogether.
We should also remove the language about all objects existing in the Default space after upgrade. That was only really relevant for folks upgrading from pre-6.5 to >= 6.5, and I sincerely hope that everyone has done that by now. It's just confusing/misleading for everyone else at this point.
kibana/docs/spaces/index.asciidoc
Lines 110 to 117 in 58f6d90
[float] | |
[[spaces-delete-started]] | |
=== Disable and version updates | |
Spaces are automatically enabled in {kib}. If you don't want use this feature, | |
you can disable it. For more information, refer to <<spaces-settings-kb,Spaces settings in {kib}>>. | |
When you upgrade {kib}, the default space contains all of your existing saved objects. |
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.
Great catch, I'll change this section to:
Starting in {kib} 8.0, the Spaces feature cannot be disabled.
* 2.0. | ||
*/ | ||
|
||
export { SimplePrivilegeSection } from './simple_privilege_section'; |
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.
You have no idea how happy I am to see this SimplePrivilegeSection
removed ❤️
FooAllAtEverythingSpace, | ||
FooAllAtNothingSpace, | ||
FooReadAtEverythingSpace, | ||
FooReadAtNothingSpace, |
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.
🏅 Thanks for observing this and not just blindly deleting the other test suites. This was done intentionally back in the day in order to reduce unnecessary duplication between the test suites.
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.
kibana-docker LGTM
Co-authored-by: Larry Gregory <lgregorydev@gmail.com>
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.
LGTM!
I think as a followup item (post FF) we should make the spaces
plugin required
within the security
plugin, and remove the small amount of dead code we have on the server to account for Spaces being disabled.
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.
Cases changes LGTM
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
To update your PR or re-run it, just comment with: |
Resolves #82467.