rest-api-spec: add missing enum options #137522
Merged
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
pquentin
added
>non-issue
:Core/Infra/REST API
elasticsearchmachine
added
v9.3.0
Team:Core/Infra
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
elasticsearchmachine
added
v9.1.8
v9.2.2
v8.19.8
and removed
v9.1.7
v9.2.1
v8.19.7
labels
Contributor
|
lgtm, but not sure how to validate the options 🤷 |
l-trotta
approved these changes
Nov 13, 2025
Collaborator
💔 Backport failed
You can use sqren/backport to manually backport by running |
pquentin
added a commit
to pquentin/elasticsearch
that referenced
this pull request
Nov 13, 2025
* rest-api-spec: add missing enum options * Allow dots in option values
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Unlike #137521, the type was already correct. The values come from the Elasticsearch specification.