[7.17] Change deprecation warning for elasticsearch.username #124717
Merged
Conversation
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
jportner
added
release_note:fix
Team:Security
|
Pinging @elastic/kibana-security (Team:Security) |
Note, I ran the i18n check script locally and it didn't catch any changes. I am leaving this commit as-is to see if CI catches the changes.
jportner
force-pushed
the
issue-124691-fix-elasticsearch-username-deprecation-warning
branch
from
4e4f41a to
781c223
Compare
watson
approved these changes
Feb 7, 2022
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
jportner
deleted the
issue-124691-fix-elasticsearch-username-deprecation-warning
branch
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.
Resolves #124691.
The Upgrade Assistant tells users to use the Elasticsearch service account CLI to create a service account token. We have discovered that this is the wrong approach, because it will only work for a single ES node, so we should instead direct users to use the API to create a service account token.
Here is what the deprecation looks like in the Upgrade Assistant with these changes:
Release note: The upgrade assistant guidance for
elasticsearch.usernamedeprecation has been updated to reflect that service account tokens should only be created using the Elasticsearch API.