Releases: hashicorp/terraform
v1.6.0-beta1
1.6.0-beta1 (August 31, 2023)
UPGRADE NOTES:
- On macOS, Terraform now requires macOS 10.15 Catalina or later; support for previous versions has been discontinued.
- On Windows, Terraform now at least Windows 10 or Windows Server 2016; support for previous versions has been discontinued.
- The S3 backend has a number of significant changes to its configuration format in this release, intended to match with recent changes in the
hashicorp/awsprovider:- Configuration settings related to assuming IAM roles now belong to a nested block
assume_role. The top-level argumentsrole_arn,session_name,external_id,assume_role_duration_seconds,assume_role_policy_arns,assume_role_tags, andassume_role_transitive_tag_keysare all now deprecated in favor of the nested equivalents. (#30495) - Configuration settings related to overriding the locations of AWS service endpoints used by the provider now belong to a nested block
endpoints. The top-level argumentsdynamodb_endpoint,iam_endpoint,endpoint(fir S3), andsts_endpointare now deprecated in favor of the nested equivalents. (#30492) - The backend now uses the following environment variables for overriding the default locations of AWS service endpoints used by the provider:
AWS_ENDPOINT_URL_DYNAMODB,AWS_ENDPOINT_URL_IAM,AWS_ENDPOINT_URL_S3, andAWS_ENDPOINT_URL_STS. The old non-standard names for these environment variables are now deprecated:AWS_DYNAMODB_ENDPOINT,AWS_IAM_ENDPOINT,AWS_S3_ENDPOINT, andAWS_STS_ENDPOINT. (#30479) - The singular
shared_credentials_fileargument is deprecated in favor of the pluralshared_credentials_files. - The
force_path_styleargument is deprecated in favor ofuse_path_stylefor consistency with the AWS SDK. (#30491)
- Configuration settings related to assuming IAM roles now belong to a nested block
NEW FEATURES:
-
terraform test: Theterraform testcommand is now generally available. This comes with a significant change to how tests are written and executed, based on feedback from the experimental phase.Terraform tests are written in
.tftest.hclfiles, containing a series ofrunblocks. Eachrunblock executes a Terraform plan and optional apply against the Terraform configuration under test and can check conditions against the resulting plan and state.
ENHANCEMENTS:
-
config: The
importblockidfield now accepts expressions referring to other values such as resource attributes, as long as the value is a string known at plan time. (#33618) -
Terraform Cloud integration: Remote plans on Terraform Cloud/Enterprise can now be saved using the
-outoption, viewed usingterraform show, and applied usingterraform applywith the saved plan filename. (#33492) -
config: Terraform can now track some additional detail about values that won't be known until the apply step, such as the range of possible lengths for a collection or whether an unknown value can possibly be null.
When this information is available, Terraform can potentially generate known results for some operations on unknown values. This doesn't mean that Terraform can immediately track that detail in all cases, but the type system now supports that and so over time we can improve the level of detail generated by built-in functions, language operators, Terraform providers, etc. (#33234)
-
config: The
tryandcanfunctions can now return more precise and consistent results when faced with unknown arguments (#33758) -
terraform show -json: Now includeserroredproperty, indicating whether the planning process halted with an error. An errored plan is not applyable. (#33372) -
core: Terraform will now skip requesting the (possibly very large) provider schema from providers which indicate during handshake that they don't require that for correct behavior, in situations where Terraform Core itself does not need the schema. (#33486)
-
backend/kubernetes: The Kubernetes backend is no longer limited to storing states below 1MiB in size, and can now scale by splitting state across multiple secrets. (#29678)
-
backend/s3: Various improvements for consistency with
hashicorp/awsprovider capabilities:assume_role_with_web_identitynested block for assuming a role with dynamic credentials such as a JSON Web Token. (#31244)- Now honors the standard AWS environment variables for credential and configuration files:
AWS_CONFIG_FILEandAWS_SHARED_CREDENTIALS_FILE. (#30493) shared_config_filesandshared_credentials_filesarguments for specifying credential and configuration files as part of the backend configuration. (#30493)- Internally the backend now uses AWS SDK for Go v2, which should address various other missing behaviors that are handled by the SDK rather than by Terraform itself. (#30443)
custom_ca_bundleargument and support for the corresponding AWS environment variable,AWS_CA_BUNDLE, for providing custom root and intermediate certificates. (#33689)ec2_metadata_service_endpointandec2_metadata_service_endpoint_modearguments and support for the corresponding AWS environment variables,AWS_EC2_METADATA_SERVICE_ENDPOINTandAWS_EC2_METADATA_SERVICE_ENDPOINT_MODEfor setting the EC2 metadata service (IMDS) endpoint. The environment variableAWS_METADATA_URLis also supported for compatibility with the AWS provider, but is deprecated. (#30444)http_proxy,insecure,use_fips_endpoint, anduse_dualstack_endpointarguments and support for the corresponding environment variables,HTTP_PROXYandHTTPS_PROXY, which enable custom HTTP proxy configurations and the resolution of AWS endpoints with extended capabilities. (#30496)sts_regionargument to use an alternative region for STS operations. (#33693)retry_modeargument and support for the correspondingAWS_RETRY_MODEenvironment variable to configure how retries are attempted. (#33692)allowed_account_idsandforbidden_account_idsarguments to prevent unintended modifications to specified environments. (#33688)
-
backend/cos: Support custom HTTP(S) endpoint and root domain for the API client. (#33656)
BUG FIXES:
- core: Transitive dependencies were lost during apply when the referenced resource expanded into zero instances. (#33403)
- cli: Terraform will no longer override SSH settings in local git configuration when installing modules. (#33592)
terraformbuilt-in provider: The upstream dependency that Terraform uses for service discovery of Terraform-native services such as Terraform Cloud/Enterprise state storage was previously not concurrency-safe, but Terraform was treating it as if it was in situations like when a configuration has multipleterraform_remote_stateblocks all using the "remote" backend. Terraform is now using a newer version of that library which updates its internal caches in a concurrency-safe way. (#33364)terraform init: Terraform will no longer allow downloading remote modules to invalid paths. (#33745)- cloud: state snapshots could not be disabled when header x-terraform-snapshot-interval is absent (#33820)
Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.5.6
v1.6.0-alpha20230816
1.6.0-alpha20230816 (Unreleased)
NEW FEATURES:
-
terraform test: The previously experimentalterraform testcommand has been moved out of experimental. This comes with a significant change in how Terraform tests are written and executed.Terraform tests are now written within
.tftest.hclfiles, controlled by a series ofrunblocks. Eachrunblock will execute a Terraform plan or apply command against the Terraform configuration under test and can execute conditions against the resultant plan and state.
ENHANCEMENTS:
- config: Terraform can now track some additional detail about values that won't be known until the apply step, such as the range of possible lengths for a collection or whether an unknown value can possibly be null. When this information is available, Terraform can potentially generate known results for some operations on unknown values. This doesn't mean that Terraform can immediately track that detail in all cases, but the type system now contains the facility for that and so over time we will improve the level of detail generated by built-in functions, language operators, Terraform providers, etc. (#33234)
- jsonplan: Added
erroredfield to JSON plan output, indicating whether a plan errored. (#33372) - cloud: Remote plans on Terraform Cloud/Enterprise can now be saved using the
-outflag, referenced in theshowcommand, and applied by specifying the plan file name. (#33492) - config: The
importblockidfield now accepts an expression referencing other values such as resource attributes, as long as the value is a string known at plan time. (#33618)
BUG FIXES:
- The upstream dependency that Terraform uses for service discovery of Terraform-native services such as Terraform Cloud/Enterprise state storage was previously not concurrency-safe, but Terraform was treating it as if it was in situations like when a configuration has multiple
terraform_remote_stateblocks all using the "remote" backend. Terraform is now using a newer version of that library which updates its internal caches in a concurrency-safe way. (#33364) - Transitive dependencies were lost during apply when the referenced resource expanded into zero instances (#33403)
- Terraform will no longer override SSH settings in local git configuration when installing modules. (#33592)
Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.5.5
v1.6.0-alpha20230802
1.6.0-alpha20230802 (August 02, 2023)
NEW FEATURES:
-
terraform test: The previously experimentalterraform testcommand has been moved out of experimental. This comes with a significant change in how Terraform tests are written and executed.Terraform tests are now written within
.tftest.hclfiles, controlled by a series ofrunblocks. Eachrunblock will execute a Terraform plan or apply command against the Terraform configuration under test and can execute conditions against the resultant plan and state.
ENHANCEMENTS:
- config: Terraform can now track some additional detail about values that won't be known until the apply step, such as the range of possible lengths for a collection or whether an unknown value can possibly be null. When this information is available, Terraform can potentially generate known results for some operations on unknown values. This doesn't mean that Terraform can immediately track that detail in all cases, but the type system now contains the facility for that and so over time we will improve the level of detail generated by built-in functions, language operators, Terraform providers, etc. (#33234)
- jsonplan: Added
erroredfield to JSON plan output, indicating whether a plan errored. (#33372) - cloud: Remote plans on Terraform Cloud/Enterprise can now be saved using the
-outflag, referenced in theshowcommand, and applied by specifying the plan file name. (#33492) - cloud: Terraform now supports setting the Terraform Cloud project via the cloud block and
TF_CLOUD_PROJECTenvironment variable. When a cloud configuration creates a new workspace it will be created in the given project. If the project does not exist it will be created. terraform workspace list will also respect listing matching workspaces in the configured project. - config: The
importblockidfield now accepts an expression referencing other values such as resource attributes, as long as the value is a string known at plan time. (#33618)
BUG FIXES:
- The upstream dependency that Terraform uses for service discovery of Terraform-native services such as Terraform Cloud/Enterprise state storage was previously not concurrency-safe, but Terraform was treating it as if it was in situations like when a configuration has multiple
terraform_remote_stateblocks all using the "remote" backend. Terraform is now using a newer version of that library which updates its internal caches in a concurrency-safe way. (#33364) - Transitive dependencies were lost during apply when the referenced resource expanded into zero instances (#33403)
- Terraform will no longer override SSH settings in local git configuration when installing modules. (#33592)
Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.5.4
v1.6.0-alpha20230719
1.6.0-alpha20230719 (Unreleased)
NEW FEATURES:
-
terraform test: The previously experimentalterraform testcommand has been moved out of experimental. This comes with a significant change in how Terraform tests are written and executed.Terraform tests are now written within
.tftestfiles, controlled by a series ofrunblocks. Eachrunblock will execute a Terraform plan or apply command against the Terraform configuration under test and can execute conditions against the resultant plan and state.
ENHANCEMENTS:
- config: Terraform can now track some additional detail about values that won't be known until the apply step, such as the range of possible lengths for a collection or whether an unknown value can possibly be null. When this information is available, Terraform can potentially generate known results for some operations on unknown values. This doesn't mean that Terraform can immediately track that detail in all cases, but the type system now contains the facility for that and so over time we will improve the level of detail generated by built-in functions, language operators, Terraform providers, etc. [GH-33234]
- jsonplan: Added
erroredfield to JSON plan output, indicating whether a plan errored. [GH-33372]
BUG FIXES:
- The upstream dependency that Terraform uses for service discovery of Terraform-native services such as Terraform Cloud/Enterprise state storage was previously not concurrency-safe, but Terraform was treating it as if it was in situations like when a configuration has multiple
terraform_remote_stateblocks all using the "remote" backend. Terraform is now using a newer version of that library which updates its internal caches in a concurrency-safe way. [GH-33364] - Transitive dependencies were lost during apply when the referenced resource expanded into zero instances [GH-33403]
Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.5.3
1.5.3 (July 12, 2023)
BUG FIXES:
- core: Terraform could fail to evaluate module outputs when they are used in a provider configuration during a destroy operation (#33462)
- backend/consul: When failing to save state,
consul CAS failed with transaction errorsno longer shows an error instance memory address, but an actual error message. (#33108) - plan renderer: Fixes crash when rendering the plan if a relevant attribute contains an integer index specified as a string. (#33475)