Manage Resources with Terraform

Use Terraform resources to manage the lifecycle of VeloDB Cloud objects. Use data sources to read existing VeloDB Cloud information without managing its lifecycle.

Common management tasks

Goal	Provider documentation
Create, update, import, or delete a warehouse	velodb_warehouse resource
Add, resize, pause, or resume a physical compute cluster	velodb_cluster resource
Read warehouse endpoints and connection metadata	velodb_warehouse_connections data source
Find other supported resources and data sources	VeloDB provider documentation

VeloDB Cloud considerations

• The provider manages physical COMPUTE clusters. It does not manage virtual clusters or SQL and OBSERVER clusters.
• Increasing both CPU and cache capacity can require two applies. First increase compute_vcpu and set cache_gb to the minimum for the new CPU size. Then apply any additional cache-only increase.
• The Management API does not return every write-only or creation-only value. Review the resource import documentation and the resulting plan before applying changes to an imported resource.
• Changes made through the VeloDB Cloud Console or Management API can cause configuration drift. Review every Terraform plan before applying it.
• Terraform state can contain warehouse administrator passwords and other sensitive values. Store state in an encrypted remote backend and restrict access to it.
• Destroying a warehouse deletes the warehouse, its clusters, and its data. For AWS BYOC, AWS resources managed separately can remain after the warehouse is deleted.

For Terraform state, import, planning, and destroy workflows, see the Terraform CLI documentation.