Skip to main content

Overview

The Terraform Exporter converts your Qovery environment configuration into Terraform manifests, enabling you to transition from UI-based setup to infrastructure-as-code management without manually writing configurations.
Build your infrastructure in the Qovery Console, then export everything as Terraform code for version control and automation.

What Gets Exported

The exporter generates a complete Terraform configuration including:
  • Environment: Name, mode, cluster assignment, variables, deployment rules
  • Services: Applications, databases, jobs, and Helm charts with all their configurations
  • Resources: Organization, project, and cluster data sources
  • Configuration: Advanced settings, ports, resource limits, auto-deploy settings
  • Secrets (optional): Environment variables and secrets

How to Export

1

Navigate to Environment

Go to the environment you want to export in the Qovery Console
2

Export

Click on the environment settings (three dots menu) and select Export as Terraform
3

Choose Options

Select whether to include secrets in the export
If you include secrets, they will be in plain text. Use environment variables or secret managers before committing to version control.
4

Download

Download the generated Terraform configuration

Using Exported Configuration

1

Import Existing Resources

Import resources to avoid recreating them:
terraform import qovery_environment.prod <environment-id>
terraform import qovery_application.api <application-id>
terraform import qovery_database.postgres <database-id>
2

Initialize and Apply

terraform init
export TF_VAR_qovery_api_token="your-api-token"
terraform plan
terraform apply
If you imported resources correctly, terraform plan should show no or minimal changes.

Best Practices

  • Never commit secrets to version control - use environment variables or secret managers
  • Import existing resources before applying to avoid recreation
  • Use remote state backend (S3, Terraform Cloud) for team collaboration
  • Keep exported configurations in separate directories per environment

Next Steps