-
Notifications
You must be signed in to change notification settings - Fork 133
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
Xpack roles:elastic: Error 400 (Bad Request): request body is required [type=parse_exception] #49
Comments
@andrescolodrero what version of the provider are you using? |
@phillbaker sorry, i forget that detail. maybe the client for v7 will need an update? |
It looks like there is an issue on 7.5: https://travis-ci.org/phillbaker/terraform-provider-elasticsearch/jobs/626767093#L1400. ESv7.4 and lower don't have issues. Two potential PRs stand out from the release notes |
Looks like the tests pass on v7.5 after fixing some permissions that didn't exist, here's the commit: 5387064. Is it possible that the values you used ended up creating invalid JSON when serialized? Did you get this error on a plan or apply? Can you try running the command again with |
With same code as before, im getting a new type of error: Error: Body Error : on roles.tf line 48, in resource "elasticsearch_xpack_role" "arion-kibana-editor": i removed the line: in code is "schema.TypeString",
|
Hm, I've been able to reproduce that: https://travis-ci.org/phillbaker/terraform-provider-elasticsearch/jobs/634034936#L1231. It comes from: terraform-provider-elasticsearch/resource_elasticsearch_xpack_role.go Lines 244 to 248 in 5387064
So, the request isn't even being sent, seems like a bug in this provider. Thanks for the additional details. |
@andrescolodrero an update on my side: fixing this will likely require changing the type of the field_security attribute. However, I did want to point out, that from the ES docs:
So there's no need to specify |
I believe this was fixed as an outcome of #59. @andrescolodrero can you try v1.0.0 to see if that fixes the issue? |
Going to close this for now, please re-open if this continues to be an issues. |
Im having this error:
Error 400 (Bad Request): request body is required [type=parse_exception]
On a 7.5.0 Cluster,
with this configuration:
The text was updated successfully, but these errors were encountered: