You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This fails for obvious reasons. However, my bug was non-obvious and the log messages with TF_LOG=debug TF_ACC=1 were not helpful. The closest seems to be:
2023-11-08T08:44:43.108-0800 [INFO] provider.terraform-provider-elasticsearch_v2.0.7: 2023/11/08 08:44:43 [INFO] couldn't create client: *errors.withStack, no active connection found: no Elasticsearch node available, *errors.withMessage: timestamp=2023-11-08T08:44:43.107-0800
2023-11-08T08:44:43.108-0800 [ERROR] vertex "elasticsearch_opensearch_role.event-trace" error: HEAD healthcheck failed: This is usually due to network or permission issues. The underlying error isn't accessible, please debug by disabling healthchecks.
2023-11-08T08:44:43.108-0800 [ERROR] vertex "elasticsearch_opensearch_role.event-trace (expand)" error: HEAD healthcheck failed: This is usually due to network or permission issues. The underlying error isn't accessible, please debug by disabling healthchecks.
Disabling healthchecks does not improve the message to indicate what the problem might be (also, it's confusing that this is still printed when healthcheck = false). Would of saved me a lot of time if the value of the url was contained somewhere in the log output.
The text was updated successfully, but these errors were encountered:
So due to a bug in my code, I effectively had my provider block defined as:
This fails for obvious reasons. However, my bug was non-obvious and the log messages with
TF_LOG=debug TF_ACC=1
were not helpful. The closest seems to be:Disabling healthchecks does not improve the message to indicate what the problem might be (also, it's confusing that this is still printed when
healthcheck = false
). Would of saved me a lot of time if the value of theurl
was contained somewhere in the log output.The text was updated successfully, but these errors were encountered: