-
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
Remove the id field from the InvalidateApiKey API #66671
Merged
ywangd
merged 1 commit into
elastic:master
from
ywangd:remove-id-for-invalidate-api-keys
Dec 22, 2020
Merged
Remove the id field from the InvalidateApiKey API #66671
ywangd
merged 1 commit into
elastic:master
from
ywangd:remove-id-for-invalidate-api-keys
Dec 22, 2020
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
ywangd
added
>deprecation
:Security/Security
Security issues without another label
v8.0.0
labels
Dec 21, 2020
Pinging @elastic/es-security (Team:Security) |
tvernum
approved these changes
Dec 21, 2020
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
simitt
added a commit
to simitt/apm-server
that referenced
this pull request
Dec 24, 2020
The ES InvalidateApiKey API does not support param ID anymore. Switch to using IDs instead. Related elastic/elasticsearch#66671
simitt
added a commit
to elastic/apm-server
that referenced
this pull request
Dec 24, 2020
The ES InvalidateApiKey API does not support param ID anymore. Switch to using IDs instead. Related elastic/elasticsearch#66671
ywangd
added a commit
to ywangd/elasticsearch
that referenced
this pull request
Oct 5, 2021
This PR restore the id field for InvaliateApiKey API so it can be used if the request explicitly requires v7 compatibility. Relates: elastic#66671
ywangd
added a commit
that referenced
this pull request
Oct 11, 2021
This PR restore the id field for InvaliateApiKey API so it can be used if the request explicitly requires v7 compatibility. Relates: #66671
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>breaking
:Security/Security
Security issues without another label
Team:Security
Meta label for security team
v8.0.0-alpha1
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.
This is a follow-up of #66317 to remove the now deprecated
id
field from the InvalidateApiKey request.