Revert addition of logstash.jdk.force setting - #19375
Merged
Merged
Conversation
… 17 (elastic#19361)" This reverts commit 7ab78e2.
This reverts commit 1b9db53.
Contributor
🤖 GitHub commentsJust comment with:
|
Member
Author
|
run exhaustive tests |
Member
Author
💚 Build Succeeded
|
12 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Release notes
[rn:skip]
What does this PR do?
Reverts addition of
logstash.jdk.forceand all references to it while we figure out the best ergonomics and deprecation path. The behavior should remain the same as in 8.19.19 whereby if a custom jdk 17 is detected a deprecation will be logged and logstash will continue to run normally.Reverts #19311 #19361