-
Notifications
You must be signed in to change notification settings - Fork 158
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
Cannot use method PATCH in Kibana Dev Tools Console #51
Comments
Hi @DJSundog, Can you tell me the curl command? Which flags and headers did you pass over the request to patch multiple Tentants? |
Hi, although this is an older one, I'd like to confirm this. In Kibana:
ends up with:
Using curl, it works:
Kibana also shows an syntax error when using |
I can confirm this is happening to me as well. For those using AWS's Elasticsearch it means their documentation doesn't work either and I had to turn the single PATCH into individual PUTs if I wanted to use the built-in console. Step 14: |
exact same issue here. curl -X patch worked for me and dev tools didnt. |
We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here). If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it. Thanks! |
Not sure if this is the right repo for this issue or not, but figure it's a good place to start.
According to the docs at https://opendistro.github.io/for-elasticsearch-docs/docs/security-access-control/api/#patch-user, to update individual attributes of an internal user one should submit a request using HTTP PATCH method.
However, the dev tools console in Kibana rejects PATCH as an allowed method:
I have confirmed that using
curl -XPATCH
with the appropriate request body does update the internal user properly.It would be useful if either:
(a) Kibana were updated to accept PATCH method in dev tools console
or
(b) The API were updated to accept POST method for endpoints currently using PATCH.
The text was updated successfully, but these errors were encountered: