Closed wb529kq closed 3 years ago
id_attribute = "org" object_id = "org"
I can't say I'm familiar with the API, but this error only occurs if the write_returns_object
or create_returns_object
flag is set, but the response doesn't indicate the object's ID in it. Basically, the provider needs to know the server-side ID of what got created so it can manage it. Have you confirmed the right id attribute is set? Perhaps debug output will show the data that is returned so you can manually confirm that the right parameters are set.
The API is a little broken the create id is "org" but the read id is a unique "public_id" returned after the create process. I couldnt immediately see a way to have a create id and a read id. The path is the same.
That sounds pretty odd indeed - but I may not follow completely. Can you share a config example and then create/read response from the server? It's possible that this provider can't help, but seeing the "guts" of request/response could help confirm.
thanks for the response I gave up with that part of the datadog API and went another direction while they fix the API to be a little more ... "sane"
anyone using this with datadog and have a working config...
Getting ... Error: Internal validation failed. Object ID is not set, but may have been created. This should never happen!