BUG FIXES:
terraform_remote_state
: fix incompatibility with states produced by Terraform 1.5 or later which include check
block results. (#33813)BUG FIXES:
BUG FIXES:
before_sensitive
/ after_sensitive
annotations in JSON plan output for deeply nested structures. This was only observed in the wild on the rancher/rancher2 provider, and resulted in glitched display in Terraform Cloud's structured plan log view. (#32543)BUG FIXES:
ignore_changes
(#32428)BUG FIXES:
BUG FIXES:
(sensitive value)
instead of sometimes as (sensitive)
(#32004)BUG FIXES:
console
when outputs contain preconditions (#32051)oidc_token
and oidc_token_file_path
properties (#31966)regex
, regexall
, and replace
functions, to avoid unbounded memory usage for maliciously-crafted patterns. This change should not affect any reasonable patterns intended for practical use. (#32135)BUG FIXES:
BUG FIXES:
ignore_changes = all
could cause persistent diffs with legacy providers (#31914)import
(#31878)NOTE:
darwin/amd64
and darwin/arm64
architectures, terraform
binaries are now built with CGO enabled. This should not have any user-facing impact, except in cases where the pure Go DNS resolver causes problems on recent versions of macOS: using CGO may mitigate these issues. Please see the upstream bug https://github.com/golang/go/issues/52839 for more details.BUG FIXES:
NEW FEATURES:
Optional attributes for object type constraints: When declaring an input variable whose type constraint includes an object type, you can now declare individual attributes as optional, and specify a default value to use if the caller doesn't set it. For example:
variable "with_optional_attribute" { type = object({ a = string # a required attribute b = optional(string) # an optional attribute c = optional(number, 127) # an optional attribute with a default value }) }
Assigning { a = "foo" }
to this variable will result in the value { a = "foo", b = null, c = 127 }
.
Added functions: startswith
and endswith
allow you to check whether a given string has a specified prefix or suffix. (#31220)
UPGRADE NOTES:
terraform show -json
: Output changes now include more detail about the unknown-ness of the planned value. Previously, a planned output would be marked as either fully known or partially unknown, with the after_unknown
field having value false
or true
respectively. Now outputs correctly expose the full structure of unknownness for complex values, allowing consumers of the JSON output format to determine which values in a collection are known only after apply.
terraform import
: The -allow-missing-config
has been removed, and at least an empty configuration block must exist to import a resource.
Consumers of the JSON output format expecting on the after_unknown
field to be only false
or true
should be updated to support the change representation described in the documentation, and as was already used for resource changes. (#31235)
AzureRM Backend: This release concludes the deprecation cycle started in Terraform v1.1 for the azurerm
backend's support of “ADAL” authentication. This backend now supports only “MSAL” (Microsoft Graph) authentication.
This follows from Microsoft's own deprecation of Azure AD Graph, and so you must follow the migration instructions presented in that Azure documentation to adopt Microsoft Graph and then change your backend configuration to use MSAL authentication before upgrading to Terraform v1.3.
When making requests to HTTPS servers, Terraform will now reject invalid handshakes that have duplicate extensions, as required by RFC 5246 section 7.4.1.4 and RFC 8446 section 4.2. This may cause new errors when interacting with existing buggy or misconfigured TLS servers, but should not affect correct servers.
This only applies to requests made directly by Terraform CLI, such as provider installation and remote state storage. Terraform providers are separate programs which decide their own policy for handling of TLS handshakes.
The following backends, which were deprecated in v1.2.3, have now been removed: artifactory
, etcd
, etcdv3
, manta
, swift
. The legacy backend name azure
has also been removed, because the current Azure backend is named azurerm
. (#31711)
ENHANCEMENTS:
timecmp
allows determining the ordering relationship between two timestamps while taking potentially-different UTC offsets into account. (#31687)moved
blocks can now describe resources moving to and from modules in separate module packages. (#31556)terraform fmt
now accepts multiple target paths, allowing formatting of several individual files at once. (#28191)terraform init
: provider installation errors now mention which host Terraform was downloading from (#31524)PlanResourceChange
for compatible providers when destroying resource instances. (#31179)BUG FIXES:
terraform show -json
: Fixed missing markers for unknown values in the encoding of partially unknown tuples and sets. (#31236)terraform output
CLI help documentation is now more consistent with web-based documentation. (#29354)terraform init
: Error messages now handle the situation where the underlying HTTP client library does not indicate a hostname for a failed request. (#31542)terraform init
: Don't panic if a child module contains a resource with a syntactically-invalid resource type name. (#31573)null
output values in a destroy plan will no longer report them as being deleted, which avoids reporting the deletion of an output value that was already absent. (#31471)terraform import
: Better handling of resources or modules that use for_each
, and situations where data resources are needed to complete the operation. (#31283)EXPERIMENTS:
This release concludes the module_variable_optional_attrs
experiment, which started in Terraform v0.14.0. The final design of the optional attributes feature is similar to the experimental form in the previous releases, but with two major differences:
optional
function-like modifier for declaring an optional attribute now accepts an optional second argument for specifying a default value to use when the attribute isn't set by the caller. If not specified, the default value is a null value of the appropriate type as before.defaults
function, previously used to meet the use-case of replacing null values with default values, will not graduate to stable and has been removed. Use the second argument of optional
inline in your type constraint to declare default values instead.If you have any experimental modules that were participating in this experiment, you will need to remove the experiment opt-in and adopt the new syntax for declaring default values in order to migrate your existing module to the stablized version of this feature. If you are writing a shared module for others to use, we recommend declaring that your module requires Terraform v1.3.0 or later to give specific feedback when using the new feature on older Terraform versions, in place of the previous declaration to use the experimental form of this feature:
terraform { required_version = ">= 1.3.0" }
For information on prior major and minor releases, see their changelogs: