-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Deprecate security implicitly disabled on trial/basic #72339
Merged
jkakavas
merged 16 commits into
elastic:7.x
from
jkakavas:deprecate-implicit-security-setting
Jul 15, 2021
Merged
Changes from 10 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
baf768a
Deprecate security implicitly disabled on trial/basic
jkakavas ad2b84c
fix tests
jkakavas eed4977
Merge remote-tracking branch 'origin/7.x' into deprecate-implicit-sec…
jkakavas 3238835
typo
jkakavas 787aa00
Merge remote-tracking branch 'origin/7.x' into deprecate-implicit-sec…
jkakavas e5e9e2a
Address feedback
jkakavas 11c5dc2
Adust deprecation criticality and message
jkakavas 59b85d7
Address feedback
jkakavas aa2df0f
fix string
jkakavas b559931
update text matcher
jkakavas 7be6983
Merge remote-tracking branch 'origin/7.x' into deprecate-implicit-sec…
jkakavas 50570d5
address feedback
jkakavas eca4496
Merge remote-tracking branch 'origin/7.x' into deprecate-implicit-sec…
jkakavas 9207bac
fix test
jkakavas 2358a8d
Merge remote-tracking branch 'origin/7.x' into deprecate-implicit-sec…
jkakavas 1ea2f73
Finalize wording for deprecation message
jkakavas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
[[migrating-7.14]] | ||
== Migrating to 7.14 | ||
++++ | ||
<titleabbrev>7.14</titleabbrev> | ||
++++ | ||
|
||
This section discusses the changes that you need to be aware of when migrating | ||
your application to {es} 7.14. | ||
|
||
See also <<release-highlights>> and <<es-release-notes>>. | ||
|
||
// * <<breaking_714_blah_changes>> | ||
// * <<breaking_714_blah_changes>> | ||
|
||
//NOTE: The notable-breaking-changes tagged regions are re-used in the | ||
//Installation and Upgrade Guide | ||
|
||
//tag::notable-breaking-changes[] | ||
|
||
[discrete] | ||
[[breaking-changes-7.14]] | ||
=== Breaking changes | ||
|
||
The following changes in {es} 7.14 might affect your applications | ||
and prevent them from operating normally. | ||
Before upgrading to 7.14, review these changes and take the described steps | ||
to mitigate the impact. | ||
|
||
NOTE: Breaking changes introduced in minor versions are | ||
normally limited to security and bug fixes. | ||
Significant changes in behavior are deprecated in a minor release and | ||
the old behavior is supported until the next major release. | ||
To find out if you are using any deprecated functionality, | ||
enable <<deprecation-logging, deprecation logging>>. | ||
|
||
[discrete] | ||
[[breaking_714_security_changes]] | ||
==== Security deprecations | ||
|
||
[[implicitly-disabled-security]] | ||
.The default behavior of disabling security on basic and trial licenses is deprecated | ||
[%collapsible] | ||
==== | ||
*Details* + | ||
Currently, security features are disabled when operating on a basic or trial | ||
license when `xpack.security.enabled` has not been explicitly set to `true`. | ||
This behavior is now deprecated. In version 8.0.0, security features will be | ||
enabled by default for all licenses, unless explicitly disabled (by setting | ||
`xpack.security.enabled` to `false`). | ||
==== |
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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Could this be better phrased as "will change the default of [xpack.security.enabled] to 'true' regardless of the license level."?
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 the suggestion Ryan. I don't have a strong opinion here, I think both versions convey the meaning equally clearly and as a non-native speaker, I can't say I see an impactful difference. Your version is shorter and I do like that. I'll ping @lockewritesdocs for an opinion and if he's also +1, I'll make the change
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 think that "will change the default of [xpack.security.enabled] to 'true'" is a little ambiguous. It almost sounds like we're moving away from the default, which is currently
[xpack.security.enabled]
totrue
. I'd suggest the following revision, which incorporates Ryan's shorter version: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 was trying to move away from "will set" because it implies the value is actually being set (for example in elasticsearch.yml) when it is not. It is a default value that we will now be applied regardless of other factors.
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.
That's a good callout @rjernst. The behavior will operate as if
[xpack.security.enabled]
istrue
. Perhaps we can explain that nuance with something like: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 don't think we're using phrases such as "The behavior will operate as if X is Y" for settings that have default value set to Y anywhere else. I find this confusing to be honest. May I suggest
A later version of Elasticsearch will set [xpack.security.enabled] to \"true\"
-->
In a later version of Elasticsearch, the value of [xpack.security.enabled] will default to \"true\"
?