Hmm, hang on - thought I was on the latest pulumi-confluent version (python), but may not have been

Ok, confirmed the issue is still there. I’m running pulumi v3.22.1 and a python pulumi script using pulumi-confluent==0.2.2 and pulumi==3.22.1. Trying to create a cluster with service_provider=‘aws’, region=‘us-west-1’, availability=‘LOW’, deployment={“sku”: ‘BASIC’} and an api for that cluster (and in the same confluent environment). But my stack ends up with its confluentindexKafkaCluster showing status “creating failed” and error message “* clusters: Oops, something went wrong”

Running with

TF_LOG=1 pulumi up -v=9 --logtostderr --yes

shows “No meta timeoutkey found in Apply()” being logged (I believe by terraform):

...
I0119 21:49:28.544403   46034 rpc.go:74] Marshaling property for RPC[Provider[confluent, 0xc001354840].Create(urn:pulumi:internal-alpha-aws::confluent-kafka::confluent:index/kafkaCluster:KafkaCluster::cluster-internal-alpha-aws).inputs]: region={us-west-1}
I0119 21:49:28.544415   46034 rpc.go:74] Marshaling property for RPC[Provider[confluent, 0xc001354840].Create(urn:pulumi:internal-alpha-aws::confluent-kafka::confluent:index/kafkaCluster:KafkaCluster::cluster-internal-alpha-aws).inputs]: serviceProvider={AWS}
I0119 21:49:28.546223   46034 eventsink.go:59] No meta timeoutkey found in Apply()
I0119 21:49:28.546265   46034 eventsink.go:62] eventSink::Debug(<{%reset%}>No meta timeoutkey found in Apply()<{%reset%}>)
     pulumi:pulumi:Stack              confluent-kafka-internal-alpha-aws  running.     2022/01/19 21:49:26 [WARN] Invalid log level: "1". Defaulting to level: TRACE. Valid levels are: [TRACE DEBUG INFO W
 +   └─ confluent:index:KafkaCluster  cluster-internal-alpha-aws          creating...
I0119 21:49:29.110437   46034 eventsink.go:59] createCluster failed {cluster-internal-alpha-aws env-3dnn0 0 0 0 us-west-1 AWS LOW {BASIC env-3dnn0} 0}, clusters: Oops, something went wrong
I0119 21:49:29.110547   46034 eventsink.go:62] eventSink::Debug(<{%reset%}>createCluster failed {cluster-internal-alpha-aws env-3dnn0 0 0 0 us-west-1 AWS LOW {BASIC env-3dnn0} 0}, clusters: Oops, something went wrong<{%reset%}>)
I0119 21:49:29.111631   46034 provider_plugin.go:1531] provider received rpc error `Unknown`: `1 error occurred:
	* clusters: Oops, something went wrong
...

OMG, this was because us-west-1 is not a supported aws region by confluent cloud 😐 https://docs.confluent.io/cloud/current/clusters/regions.html. Worked with us-west-2.

Well, problem solved.. Wish there could’ve been a nicer error message.