v1.5.23 provider causing errors running plan (or apply) on eventstorecloud_project

[samsonquantifi]

Related to https://github.com/EventStore/terraform-provider-eventstorecloud/issues/83

Upon upgrade of the provider to 1.5.23, we are now having trouble running plans/apply consistently

We get this running the plan

╷
│ Error: Internal Server Error, try again later
│
│   with eventstorecloud_project.<REDACTED>,
│   on eventstorecloud.tf line 15, in resource "eventstorecloud_project" "<REDACTED>":
│   15: resource "eventstorecloud_project" "<REDACTED>" {
│
╵
Releasing state lock. This may take a few moments...

samsonnguyen@Samsons-MBP credit-app % terraform -v
Terraform v1.4.6
on darwin_arm64
+ provider registry.terraform.io/auth0/auth0 v0.48.0
+ provider registry.terraform.io/datadog/datadog v3.26.0
+ provider registry.terraform.io/eventstore/eventstorecloud v1.5.23
+ provider registry.terraform.io/hashicorp/aws v5.1.0
+ provider registry.terraform.io/hashicorp/dns v3.3.2
+ provider registry.terraform.io/hashicorp/helm v2.10.1
+ provider registry.terraform.io/hashicorp/http v3.3.0
+ provider registry.terraform.io/hashicorp/kubernetes v2.21.1
+ provider registry.terraform.io/mongodb/mongodbatlas v1.9.0

Running the plan with TF_LOG=json

{"@level":"error","@message":"vertex \"eventstorecloud_project.REDACTED\" error: Internal Server Error, try again later","@timestamp":"2023-06-07T09:29:58.028741-06:00"}
{"@level":"trace","@message":"vertex \"eventstorecloud_project.re\": visit complete, with errors","@timestamp":"2023-06-07T09:29:58.028767-06:00"}
{"@level":"trace","@message":"dag/walk: upstream of \"root\" errored, so skipping","@timestamp":"2023-06-07T09:29:58.028833-06:00"}
{"@level":"trace","@message":"vertex \"eventstorecloud_project.REDACTED (expand)\": dynamic subgraph encountered errors: Internal Server Error, try again later","@timestamp":"2023-06-07T09:29:58.028888-06:00"}
{"@level":"error","@message":"vertex \"eventstorecloud_project.REDACTED (expand)\" error: Internal Server Error, try again later","@timestamp":"2023-06-07T09:29:58.028895-06:00"}
{"@level":"trace","@message":"vertex \"eventstorecloud_project.REDACTED (expand)\": visit complete, with errors","@timestamp":"2023-06-07T09:29:58.028898-06:00"}
{"@level":"trace","@message":"dag/walk: upstream of \"eventstorecloud_network.credit_app (expand)\" errored, so skipping","@timestamp":"2023-06-07T09:29:58.028973-06:00"}
{"@level":"trace","@message":"dag/walk: upstream of \"eventstorecloud_peering.credit_app (expand)\" errored, so skipping","@timestamp":"2023-06-07T09:29:58.029024-06:00"}
{"@level":"trace","@message":"dag/walk: upstream of \"eventstorecloud_managed_cluster.REDACTED (expand)\" errored, so skipping","@timestamp":"2023-06-07T09:29:58.029051-06:00"}

Unfortunately, I'm not able to find much else to indicate what the "internal server errors" are..

[alexeyzimarev]

That seems like a known issue in the API, which also happens if you use the UI. We are working on fixing it now, but it's quote large.

Basically, it's not a TF provider issue, it is happening in the ES Cloud API backend.