v0.10.0
What's Changed
Endpoint configuration changes
This version introduces the ability and requirement to set certain parameters for Endpoints as properties of the endpoint resource. See today's https://www.aptible.com/changelog announcement and the provider documentation for more details. You will need to move certain app environment variables to endpoint properties, as appropriate.
The following environment variables are impacted:
- DISABLE_WEAK_CIPHER_SUITES
- FORCE_SSL
- IDLE_TIMEOUT
- MAINTENANCE_PAGE_URL
- RELEASE_HEALTHCHECK_TIMEOUT
- SHOW_ELB_HEALTHCHECKS
- SSL_CIPHERS_OVERRIDE
- SSL_PROTOCOLS_OVERRIDE
- STRICT_HEALTH_CHECKS
They should be instead specified as follows, for example:
resource "aptible_endpoint" "example_endpoint" {
env_id = data.aptible_environment.example.env_id
resource_id = aptible_app.example.app_id
resource_type = "app"
process_type = "cmd"
endpoint_type = "https"
default_domain = true
platform = "alb"
// newly added option examples:
idle_timeout = 120
force_ssl = true
maintenance_page_url = "https://example.com/maintenance.html"
release_healthcheck_timeout = 90
strict_health_checks = false
show_elb_healthchecks = true
ssl_protocols_override = "TLSv1.3"
}
App image configuration change
This version also makes docker_image/private_registry_username/private_registry_password properties of the app. You will also need to use these properties instead of the (now legacy) environment variables:
The following environment variables are impacted:
- APTIBLE_DOCKER_IMAGE
- APTIBLE_PRIVATE_REGISTRY_USERNAME
- APTIBLE_PRIVATE_REGISTRY_PASSWORD
resource "aptible_app" "example-app" {
env_id = data.aptible_environment.example.env_id
handle = "example-app"
docker_image = "quay.io/your-org/your-image"
// Optional:
private_registry_username = "registry_username"
private_registry_password = "registry_password"
}
Full Changelog: v0.9.24...v0.10.0