Xpack settings fixes #2998
Merged
Xpack settings fixes #2998
Conversation
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
Contributor
|
Following you can find the validation results for the API you have changed.
You can validate this API yourself by using the |
Contributor
|
Following you can find the validation results for the API you have changed.
You can validate this API yourself by using the |
github-actions bot
pushed a commit
that referenced
this pull request
Oct 14, 2024
* xpack settings fixes * correct ml place (cherry picked from commit 0259789)
l-trotta
added a commit
that referenced
this pull request
Oct 14, 2024
* xpack settings fixes * correct ml place (cherry picked from commit 0259789) Co-authored-by: Laura Trotta <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The ml field in NodeInfoXpackSecurity is used in start-local.
A java user reported that having an anonymous realm means the realm field is null (and according to the documentation, probably also the token field).
Unfortunately I couldn't find any server side proof, let's see what the validation says.