confluentinc/ccloud-tools

Resource 'google_compute_instance_template.kafka_connect' not found

Opened this issue · 1 comments

After modifying variables.tf to change the region from us-east1 to asia-southeast1, and the number of Connect nodes from 1->3 and the number of ksql nodes from 1->3; the plan stage fails with:

Error: Error running plan: 3 error(s) occurred:

  • google_compute_region_instance_group_manager.kafka_connect: 3 error(s) occurred:

  • google_compute_region_instance_group_manager.kafka_connect[1]: Resource 'google_compute_instance_template.kafka_connect' not found for variable 'google_compute_instance_template.kafka_connect.self_link'

  • google_compute_region_instance_group_manager.kafka_connect[0]: Resource 'google_compute_instance_template.kafka_connect' not found for variable 'google_compute_instance_template.kafka_connect.self_link'

  • google_compute_region_instance_group_manager.kafka_connect[2]: Resource 'google_compute_instance_template.kafka_connect' not found for variable 'google_compute_instance_template.kafka_connect.self_link'

  • data.template_file.control_center_properties: 1 error(s) occurred:

  • data.template_file.control_center_properties: Resource 'google_compute_global_address.kafka_connect' not found for variable 'google_compute_global_address.kafka_connect.address'

  • google_compute_region_instance_group_manager.ksql_server: 3 error(s) occurred:

  • google_compute_region_instance_group_manager.ksql_server[0]: Resource 'google_compute_instance_template.ksql_server' not found for variable 'google_compute_instance_template.ksql_server.self_link'

  • google_compute_region_instance_group_manager.ksql_server[2]: Resource 'google_compute_instance_template.ksql_server' not found for variable 'google_compute_instance_template.ksql_server.self_link'

  • google_compute_region_instance_group_manager.ksql_server[1]: Resource 'google_compute_instance_template.ksql_server' not found for variable 'google_compute_instance_template.ksql_server.self_link'

I will investigate this further. Still, need to replicate the issue here on my end.