Update rest-api-spec 8.15 #2876
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
requested review from
Anaethelion,
ezimuel,
flobernd,
JoshMock,
l-trotta,
miguelgrinberg,
picandocodigo,
pquentin,
srikanthmanvi,
swallez and
technige
github-actions
bot
force-pushed
the
automated/rest-api-spec-update-8.15
branch
from
466a098 to
dc50e1a
Compare
| @@ -7,8 +7,7 @@ | |||
| "stability": "stable", | |||
| "visibility": "public", | |||
| "headers": { | |||
| "accept": ["application/json"], | |||
| "content_type": ["application/json"] | |||
| "accept": ["application/json"] | |||
There was a problem hiding this comment.
@pquentin isn't this what you fixed the other day for the python client? is there a way we can ignore this?
There was a problem hiding this comment.
Yes! I opened elastic/elasticsearch#112581 late last week to fix this but it took a bit of time to be merged and backported to 8.15. Then the Elasticsearch build was failing over the weekend so there was no available artifact with the changes. Thankfully the Elasticsearch build passed during the night and this diff was thus removed automatically from this pull request.
|
The validation errors seem to be outdated, the two missing parameters were recently added |
github-actions
bot
force-pushed
the
automated/rest-api-spec-update-8.15
branch
from
dc50e1a to
f89b77d
Compare
Actually, the errors here got solved because a change in Elasticsearch resolved the diff between the JSON spec and the Elasticsearch specification. It's good new, not bad news! |
As titled.