terraform-provider-qovery

What's Changed

https://github.com/Qovery/terraform-provider-qovery/pull/301

• Fix container entrypoint
• Add user agent for advanced settings to have coherent origin when updating advanced settings

https://github.com/Qovery/terraform-provider-qovery/pull/302

Add a new attribute disk_size on cluster resource. It takes the current value of your cluster if none set

What's Changed

chore: Use terraform plugin framework 1.4.2 https://github.com/Qovery/terraform-provider-qovery/pull/299

fix: Expose Command for healthchecks https://github.com/Qovery/terraform-provider-qovery/pull/300

What's Changed

Add new container registries (https://github.com/Qovery/terraform-provider-qovery/pull/284)

Now, you can declare 3 new container registries:

• github registry (kind="GITHUB_CR")
• gitlab registry (kind="GITHUB_CR")
• any generic registry (kind="GENERIC_CR")

The following fields are required:

• config with username and password
• url that must point to the good registry:
  • https://ghcr.io for GITHUB_CR
  • https://registry.gitlab.com for GITLAB_CR

More info in our api doc: https://api-doc.qovery.com/#tag/Container-Registries/operation/createContainerRegistry

What's Changed

feat: Add custom domains for containers

https://github.com/Qovery/terraform-provider-qovery/pull/277

What's Changed

Fix documentation for override variables

https://github.com/Qovery/terraform-provider-qovery/pull/280

What's Changed

feat: Add documentation for aliases & overrides: https://github.com/Qovery/terraform-provider-qovery/pull/273

The feature related to this documentation is available here: https://github.com/Qovery/terraform-provider-qovery/releases/tag/v0.18.4

What's Changed

feat: Add service advanced settings https://github.com/Qovery/terraform-provider-qovery/commit/88617100e1e89f2287671bb4143bf4ac3cf15930

The purpose of this change is to allow to set any service advanced settings using a pure json, e.g for an application resource:

resource "qovery_application" "app" {
   // [...]
   advanced_settings_json = jsonencode({
      "network.ingress.proxy_body_size_mb": 200,
      "network.ingress.enable_cors": true
   })
}

ℹ️ You can set only the advanced settings you want to modify, it is not mandatory to set every advanced settings (the default value will be applied for non-set advanced settings)

You can refer to our api documentation to know which advanced settings are available, e.g for application resource https://api-doc.qovery.com/#tag/Applications/operation/getDefaultApplicationAdvancedSettings

refacto: Adapt cluster advanced settings in pure json https://github.com/Qovery/terraform-provider-qovery/commit/e9fbd84530c92198eb43260a35b9d5c16389ac2e

To align with services advanced settings, the cluster advanced settings are also set using pure json, e.g:

resource "qovery_cluster" "cluster" {
   // [...]
   advanced_settings_json = jsonencode({
      "aws.cloudwatch.eks_logs_retention_days": 90,
      "aws.vpc.enable_s3_flow_logs": false
   })
}

ℹ️ You can set only the advanced settings you want to modify, it is not mandatory to set every advanced settings (the default value will be applied for non-set advanced settings)

You can refer to our api documentation to know which advanced settings are available: https://api-doc.qovery.com/#tag/Clusters/operation/getDefaultClusterAdvancedSettings

⚠️ If you already had avanced_settings declared using the old way, all you have to do is to embed your current advanced_settings property with the native terraform function jsonencode() as shown in the example above