Confusing behavior of `warehouse_id` vs. warehouse name in ClickHouse Terraform provider

[monometa]

While working with ClickHouse Cloud Terraform provider (clickhouse_service resource), we discovered an inconsistency between the Cloud Console UI and Terraform.

• In UI it is possible to rename a warehouse (change its name). From Attribute "warehouse_id" cannot be specified when "password_hash" is specified #306 (comment) it seems it should be otherwise
• In Terraform the warehouse_id argument exists on the service resource (docs link), but this appears to map to an internal UUID, not to the display name.

What we expected

• That renaming a warehouse in UI would either:
  1. be detected by Terraform as a harmless name change (no recreate), or
  2. expose a warehouse_name attribute in Terraform that matches the UI field.

What actually happens

• After renaming a warehouse in UI, running terraform plan shows no changes — which suggests the provider ignores the display name completely.
• From our testing:
  • warehouse_id = internal UUID, stable and hidden from UI.
  • Renaming in UI does not break existing pipelines.
  • But Terraform has no way to manage the visible warehouse name, only the internal ID.

Why this is confusing

• The docs are not explicit that warehouse_id is an internal UUID and not the visible name.
• This creates uncertainty: is manual renaming supported and safe, or will it lead to resource recreation?
• Our use case: multi-tenant setup where warehouse naming in UI matters (primary vs. secondary services). We would like to control visible warehouse names via Terraform or at least be sure renames are safe.

Question

• Is it expected that warehouse_id refers only to the internal UUID?
• Can the provider expose a warehouse_name field that controls the display name in UI?
• If not, what is the recommended way to manage warehouse naming in a Terraform-first workflow?

[monometa]

Hello folks,

We are currently in active development and using this provider, so your insights would be really helpful.

Tagging @whites11 since you previously provided input on a similar topic

[GMartinez-Sisti]

Hi @monometa, thanks for reporting. Let us run some tests and we'll get back to you soon.

[GMartinez-Sisti]

After running some simple tests, I can confirm this behavior. Once a warehouse service is created the name of the warehouse is taken from the first service, suffixed with warehouse and it cannot be changed via terraform. The individual service names are still able to be managed from the clickhouse_service resources.

I'll report this internally so we can brainstorm how to address this, maybe an optional resource for managing the warehouse entity would work? Let me know if you have any opinions on this.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove no-issue-activity label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.

[benben]

ran into the same thing

I'll report this internally so we can brainstorm how to address this, maybe an optional resource for managing the warehouse entity would work? Let me know if you have any opinions on this.

additional resource makes sense and then you can reference

warehouse_id = clickhouse_warehouse.mywarehouse.id

from the service

[adepollo-kode]

Just commenting to note that having a Terraform resource to manage the warehouse entity would be helpful -- our team is currently building out IaC for managing our Clickhouse cloud resources and it'd be nice to be able to use the same IaC suite to manage warehouses for organizing our services.