Releases: hashicorp/terraform
v1.10.0-alpha20240717
1.10.0-alpha20240717 (July 17, 2024)
EXPERIMENTS:
Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases.
ephemeral_values
: This language experiment introduces a new special kind of value which Terraform allows to change between the plan phase and the apply phase, and between plan/apply rounds. Ephemeral values are never persisted in saved plan files or state snapshots, and so can only be used in parts of the language that don't require values to persist in those artifacts. Ephemeral input values are the main initial example of this concept, allowing the use of input variables to provide dynamic credentials that must change between plan and apply.terraform test
accepts a new option-junit-xml=FILENAME
. If specified, and if the test configuration is valid enough to begin executing, then Terraform writes a JUnit XML test result report to the given filename, describing similar information as included in the normal test output. (#34291)- The new command
terraform rpcapi
exposes some Terraform Core functionality through an RPC interface compatible withgo-plugin
. The exact RPC API exposed here is currently subject to change at any time, because it's here primarily as a vehicle to support the Terraform Stacks private preview and so will be broken if necessary to respond to feedback from private preview participants, or possibly for other reasons. Do not use this mechanism yet outside of Terraform Stacks private preview. - The experimental "deferred actions" feature, enabled by passing the
-allow-deferral
option toterraform plan
, permitscount
andfor_each
arguments inmodule
,resource
, anddata
blocks to have unknown values and allows providers to react more flexibly to unknown values. This experiment is under active development, and so it's not yet useful to participate in this experiment
Previous Releases
For information on prior major and minor releases, refer to their changelogs:
v1.9.2
v1.9.1
1.9.1 (July 3, 2024)
UPGRADE NOTES:
- Library used by Terraform (hashicorp/go-getter) for installing/updating modules was upgraded from v1.7.4 to v1.7.5. This addresses CVE-2024-6257. This change may have a negative effect on performance of
terraform init
orterraform get
in case of larger git repositories. Please do file an issue if you find the performance difference noticable. (#35376)
BUG FIXES:
v1.9.0
1.9.0 (June 26, 2024)
If you are upgrading from an earlier minor release, please refer to the Terraform v1.9 Upgrade Guide.
NEW FEATURES:
- Input variable validation rules can refer to other objects: Previously input variable validation rules could refer only to the variable being validated. Now they are general expressions, similar to those elsewhere in a module, which can refer to other input variables and to other objects such as data resources.
templatestring
function: a new built-in function which is similar totemplatefile
but designed to render templates obtained dynamically, such as from a data resource result.
ENHANCEMENTS:
terraform plan
: Improved presentation of OPA and Sentinel policy evaluations in HCP Terraform remote runs, for logical separation.terraform init
now accepts a-json
option. If specified, enables the machine readable JSON output. (#34886)terraform test
: Test runs can now pass sensitive values to input variables while preserving their dynamic sensitivity. Previously sensitivity would be preserved only for variables statically declared as being sensitive, usingsensitive = true
. (#35021)- config: Input variable validation rules can now refer to other objects in the same module. (#34955)
- config:
templatestring
function allows rendering a template provided as a string. (#34968, #35224, #35285) - core: Performance improvement during graph building for configurations with an extremely large number of
resource
blocks. (#35088) - built-in
terraform
provider: Allowsmoved
block refactoring from thehashicorp/null
providernull_resource
resource type to theterraform_data
resource type. (#35163) terraform output
withcloud
block: Terraform no longer suggests that data loss could occur when outputs are not available. (#35143)terraform console
: Now has basic support for multi-line input in interactive mode. (#34822)
If an entered line contains opening parentheses/etc that are not closed, Terraform will await another line of input to complete the expression. This initial implementation is primarily intended to support pasting in multi-line expressions from elsewhere, rather than for manual multi-line editing, so the interactive editing support is currently limited.- cli: Reduced copying of state to improve performance with large numbers of resources. (#35164)
removed
blocks can now declare destroy-time provisioners which will be executed when the associated resource instances are destroyed. (#35230)
BUG FIXES:
remote-exec
provisioner: Each remote connection will now be closed immediately after use. (#34137)- backend/s3: Fixed the digest value displayed for DynamoDB/S3 state checksum mismatches. (#34387)
terraform test
: Fix bug in which non-Hashicorp providers required by testing modules and initialised within the test files were assigned incorrect registry addresses. (#35161)- config: The
templatefile
function no longer returns a "panic" error if the template file path is marked as sensitive. Instead, the template rendering result is also marked as sensitive. (#35180) - config:
import
blocks which referenced resources in non-existent modules were silently ignored when they should have raised an error (#35330) terraform init
: When selecting a version for a provider that has both positive and negative version constraints for the same prerelease -- e.g.1.2.0-beta.1, !1.2.0-beta.1
-- the negative constraint will now overrule the positive, for consistency with how negative constraints are handled otherwise. Previously Terraform would incorrectly treat the positive as overriding the negative if the specified version was a prerelease. (#35181)import
:import
blocks could block a destroy operation if the target resource was already deleted (#35272)cli
: plan output was missing blocks which were entirely unknown (#35271)cli
: fix crash when runningproviders mirror
with an incomplete lock file (#35322)- core: Changing
create_before_destroy
when replacing an instance, then applying with-refresh=false
would order the apply operations incorrectly (#35261) - core: Resource addresses that start with the optional
resource.
prefix will now be correctly parsed when used as an address target. (#35333)
UPGRADE NOTES:
terraform test
: It is no longer valid to specify version constraints within provider blocks within .tftest.hcl files. Instead, version constraints must be supplied within the main configuration where the provider is in use.import
: Invalidimport
blocks pointing to nonexistent modules were mistakenly ignored in prior versions. These will need to be fixed or removed in v1.9.
Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.9.0-rc3
version: prepare for v1.9.0-rc3 release
v1.10.0-alpha20240619
1.10.0-alpha20240619 (June 19, 2024)
EXPERIMENTS:
Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases.
ephemeral_values
: This language experiment introduces a new special kind of value which Terraform allows to change between the plan phase and the apply phase, and between plan/apply rounds. Ephemeral values are never persisted in saved plan files or state snapshots, and so can only be used in parts of the language that don't require values to persist in those artifacts. Ephemeral input values are the main initial example of this concept, allowing the use of input variables to provide dynamic credentials that must change between plan and apply.terraform test
accepts a new option-junit-xml=FILENAME
. If specified, and if the test configuration is valid enough to begin executing, then Terraform writes a JUnit XML test result report to the given filename, describing similar information as included in the normal test output. (#34291)- The new command
terraform rpcapi
exposes some Terraform Core functionality through an RPC interface compatible withgo-plugin
. The exact RPC API exposed here is currently subject to change at any time, because it's here primarily as a vehicle to support the Terraform Stacks private preview and so will be broken if necessary to respond to feedback from private preview participants, or possibly for other reasons. Do not use this mechanism yet outside of Terraform Stacks private preview. - The experimental "deferred actions" feature, enabled by passing the
-allow-deferral
option toterraform plan
, permitscount
andfor_each
arguments inmodule
,resource
, anddata
blocks to have unknown values and allows providers to react more flexibly to unknown values. This experiment is under active development, and so it's not yet useful to participate in this experiment
Previous Releases
For information on prior major and minor releases, refer to their changelogs:
v1.9.0-rc2
Prepare for v1.9.0-rc2 release
v1.9.0-rc1
version: Prepare for v1.9.0-rc1 release
v1.10.0-alpha20240606
1.10.0-alpha20240606 (June 6, 2024)
EXPERIMENTS:
Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases.
ephemeral_values
: This language experiment introduces a new special kind of value which Terraform allows to change between the plan phase and the apply phase, and between plan/apply rounds. Ephemeral values are never persisted in saved plan files or state snapshots, and so can only be used in parts of the language that don't require values to persist in those artifacts. Ephemeral input values are the main initial example of this concept, allowing the use of input variables to provide dynamic credentials that must change between plan and apply.terraform test
accepts a new option-junit-xml=FILENAME
. If specified, and if the test configuration is valid enough to begin executing, then Terraform writes a JUnit XML test result report to the given filename, describing similar information as included in the normal test output. (#34291)- The new command
terraform rpcapi
exposes some Terraform Core functionality through an RPC interface compatible withgo-plugin
. The exact RPC API exposed here is currently subject to change at any time, because it's here primarily as a vehicle to support the Terraform Stacks private preview and so will be broken if necessary to respond to feedback from private preview participants, or possibly for other reasons. Do not use this mechanism yet outside of Terraform Stacks private preview. - The experimental "deferred actions" feature, enabled by passing the
-allow-deferral
option toterraform plan
, permitscount
andfor_each
arguments inmodule
,resource
, anddata
blocks to have unknown values and allows providers to react more flexibly to unknown values. This experiment is under active development, and so it's not yet useful to participate in this experiment
Previous Releases
For information on prior major and minor releases, refer to their changelogs: