[New Feature] Custom domain improvement

News
1

Hello all,

As you may know in our last changelog, a new option is available to indicate that a domain is behind a CDN.

image

Benefits

We are using this new option internally to handle domain checks at the end of the deployments:

  • if your domain is behind a CDN, no check is done
  • otherwise, a check is made to ensure your domain is configured correctly

Therefore this new field adds more granularity: before, it was managed by the advanced setting deployment.custom_domain_check_enabled at service level.

Impacts

The advanced setting deployment.custom_domain_check_enabled is now deprecated and no longer used by Qovery.

:warning: We plan to remove this advanced setting by the 15th of September :warning:

Please upgrade to the latest CLI & Terraform Provider versions and update your script to set the correct value for this option instead of relying on the advanced settings value:

  • CLI command introduces a new parameter --is-behind-a-cdn
qovery container domain create --domain "mydomain.com" --container "mycontainer" --environment "myenvironment" --is-behind-a-cdn=true
  • Terraform provider introduces a new field in the application, container and helm resources in the custom_domains property:
[...]
custom_domains = [
  {
    domain = "mydomain"
    generate_certificate = false
    use_cdn = true
  }
]
[...]
2 Likes
2

Change done

The advanced setting has been removed.
As said in the original post, the migration was already done since beginning of August so no impact expected.

If you used the advanced setting deployment.custom_domain_check_enabled in your terraform files, you can safely remove it from the attribute advanced_settings_json. It concerns the following resources: