-
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
Add v7 restCompat for invalidating API key with the id field #78664
Merged
ywangd
merged 5 commits into
elastic:master
from
ywangd:rest-compat-invaidate-api-key-id
Oct 11, 2021
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
881b88d
Add v7 restCompat for invalidating API key with the id field
ywangd e3ab636
Merge branch 'master' into rest-compat-invaidate-api-key-id
elasticmachine 3a7bc64
Merge remote-tracking branch 'origin/master' into rest-compat-invaida…
ywangd d3dc1b8
Unmute test
ywangd a90ff98
Merge remote-tracking branch 'origin/master' into rest-compat-invaida…
ywangd 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
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.
Is there a reason this isn't a
static final
field like the non-compat parser?I'm not particularly fussed either way, it just surprised me.
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.
My thinking is to minimize the overhead of restCompat to normal v8 usage (at the same time accept a bit more overhead for restCompat). So this v7 parser does not have to exist if client never uses v7 rest compat. It's probably a marginal saving. But recent focus on performance issue led me to this.