Closed ness-carlosherreraperez closed 1 month ago
More details from the TF Debug (I retried with 1.65.0):
module.cc_flink_kafka_blueprint.module.flink.confluent_flink_compute_pool.main: Creating...
2024-05-07T17:12:49.984-0300 [INFO] Starting apply for module.cc_flink_kafka_blueprint.module.flink.confluent_flink_compute_pool.main
2024-05-07T17:12:49.984-0300 [DEBUG] module.cc_flink_kafka_blueprint.module.flink.confluent_flink_compute_pool.main: applying the planned Create change
2024-05-07T17:12:49.985-0300 [DEBUG] provider.terraform-provider-confluent_1.65.0: Creating new Flink Compute Pool: {"spec":{"cloud":"AWS","display_name":"transport_data-flink-compute-pool","environment":{"id":"env-2jjnvm","related":"","resource_name":""},"max_cfu":5,"region":"us-east-1"}}: @caller=src/github.com/confluentinc/terraform-provider-confluent/internal/provider/resource_flink_compute_pool.go:128 tf_provider_addr=provider tf_rpc=ApplyResourceChange @module=provider tf_req_id=439e3dad-c0ab-18fe-612f-3f2f1ea400bb tf_resource_type=confluent_flink_compute_pool timestamp=2024-05-07T17:12:49.985-0300
2024-05-07T17:12:49.985-0300 [DEBUG] provider.terraform-provider-confluent_1.65.0: 2024/05/07 17:12:49 [DEBUG] POST https://api.confluent.cloud/fcpm/v2/compute-pools
2024-05-07T17:12:50.606-0300 [DEBUG] State storage *statemgr.Filesystem declined to persist a state snapshot
2024-05-07T17:12:50.606-0300 [ERROR] vertex "module.cc_flink_kafka_blueprint.module.flink.confluent_flink_compute_pool.main" error: error creating Flink Compute Pool "": undefined response type
╷
│ Error: error creating Flink Compute Pool "": undefined response type
│
│ with module.cc_flink_kafka_blueprint.module.flink.confluent_flink_compute_pool.main,
│ on .terraform/modules/cc_flink_kafka_blueprint/modules/confluent/cc_flink/main.tf line 1, in resource "confluent_flink_compute_pool" "main":
│ 1: resource "confluent_flink_compute_pool" "main" {
│
╵
Apparently, it is fixed without doing anything 🤷♂️
Since this week with:
I'm getting this error, creating a
confluent_flink_compute_pool
:I've been trying to find any explanation; this is part of a module, but we've tested this code several times with 1.6.x, with no issues. I'm gonna try to revert back to the old provider and see if it helps, but if someone has an idea, or if this is indeed a bug, It would be helpful to know :)
Thank you! Carlos