From 00bd1c0222bb4b06b71f4a51a236d139d5e8b2c9 Mon Sep 17 00:00:00 2001 From: srikantpanda Date: Wed, 24 Jun 2026 22:19:36 +0530 Subject: [PATCH] fix(datastore/postgres/gcp-cloudsql): read project_id, not project The three GCP datastore modules consume the same @facets/gcp_cloud_account provider input, but postgres/gcp-cloudsql declared the attribute as `project` while mysql/gcp-cloudsql and redis/gcp-memorystore use `project_id`. Both work today only because the resource-type system passes the whole interface object; the drift breaks the moment the output schema is tightened to one canonical name. Align on project_id (matches the two siblings and GCP API naming). Co-Authored-By: Claude Opus 4.8 (1M context) --- modules/datastore/postgres/gcp-cloudsql/1.0/variables.tf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/datastore/postgres/gcp-cloudsql/1.0/variables.tf b/modules/datastore/postgres/gcp-cloudsql/1.0/variables.tf index 17e1dc5a..5bcf2e55 100644 --- a/modules/datastore/postgres/gcp-cloudsql/1.0/variables.tf +++ b/modules/datastore/postgres/gcp-cloudsql/1.0/variables.tf @@ -82,7 +82,7 @@ variable "inputs" { type = object({ gcp_provider = object({ attributes = object({ - project = string + project_id = string credentials = string }) })