Update dependency hashicorp/terraform to v1.7.0 #79
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.6.6
->1.7.0
Release Notes
hashicorp/terraform (hashicorp/terraform)
v1.7.0
Compare Source
1.7.0 (January 17, 2024)
UPGRADE NOTES:
Input validations are being restored to the state file in this version of Terraform. Due to a state interoperability issue (#33770) in earlier versions, users that require interaction between different minor series should ensure they have upgraded to the following patches:
This is important for users with
terraform_remote_state
data sources reading remote state across different versions of Terraform.nonsensitive
function no longer raises an error when applied to a value that is already non-sensitive. (#33856)terraform graph
now produces a simplified graph describing only relationships between resources by default, for consistency with the granularity of information returned by other commands that emphasize resources as the main interesting object type and de-emphasize the other "glue" objects that connect them.The type of graph that earlier versions of Terraform produced by default is still available with explicit use of the
-type=plan
option, producing an approximation of the real dependency graph Terraform Core would use to construct a plan.terraform test
: Simplify the ordering of destroy operations during test cleanup to simple reverse run block order. (#34293)backend/s3: The
use_legacy_workflow
argument now defaults tofalse
. The backend will now search for credentials in the same order as the default provider chain in the AWS SDKs and AWS CLI. To revert to the legacy credential provider chain ordering, set this value totrue
. This argument, and the ability to use the legacy workflow, is deprecated. To encourage consistency with the AWS SDKs, this argument will be removed in a future minor version.NEW FEATURES:
terraform test
: Providers, modules, resources, and data sources can now be mocked during executions ofterraform test
. The following new blocks have been introduced within.tftest.hcl
files:mock_provider
: Can replace provider instances with mocked providers, allowing tests to execute incommand = apply
mode without requiring a configured cloud provider account and credentials. Terraform will create fake resources for mocked providers and maintain them in state for the lifecycle of the given test file.override_resource
: Specific resources can be overridden so Terraform will create a fake resource with custom values instead of creating infrastructure for the overridden resource.override_data
: Specific data sources can be overridden so data can be imported into tests without requiring real infrastructure to be created externally first.override_module
: Specific modules can be overridden in their entirety to give greater control over the returned outputs without requiring in-depth knowledge of the module itself.removed
block for refactoring modules: Module authors can now record in source code when a resource or module call has been removed from configuration, and can inform Terraform whether the corresponding object should be deleted or simply removed from state.This effectively provides a configuration-driven workflow to replace
terraform state rm
. Removing an object from state is a new type of action which is planned and applied like any other. Theterraform state rm
command will remain available for scenarios in which directly modifying the state file is appropriate.BUG FIXES:
cd
failure. (#34128)terraform test
: Stop attempting to destroy run blocks that have no actual infrastructure to destroy. This fixes an issue where attempts to destroy "verification" run blocks that load only data sources would fail if the underlying infrastructure referenced by the run blocks had already been destroyed. (#34331)terraform test
: Improve error message for invalid run block names. (#34469)terraform test
: Fix bug where outputs in "empty" modules were not available to the assertions from Terraform test files. (#34482)local-exec
andfile
provisioners connecting to remote hosts using SSH. (#34426)ENHANCEMENTS:
terraform test
: Providers defined within test files can now reference variables from their configuration that are defined within the test file. (#34069)terraform test
: Providers defined within test files can now reference outputs from run blocks. (#34118)terraform test
: Terraform functions are now available within variables and provider blocks within test files. (#34204)terraform test
: Terraform will now load variables from anyterraform.tfvars
within the testing directory, and apply the variable values to tests within the same directory. (#34341)terraform graph
: Now produces a simplified resources-only graph by default. (#34288)terraform console
: Now supports a-plan
option which allows evaluating expressions against the planned new state, rather than against the prior state. This provides a more complete set of values for use in console expressions, at the expense of a slower startup time due first calculating the plan. (#34342)import
:for_each
can now be used to expand theimport
block to handle multiple resource instances (#33932)postcondition
block or aprevent_destroy
setting, Terraform will now include that proposed change in the plan output alongside the relevant error, whereas before the error would replace the proposed change in the output. (#34312).terraformignore
: improve performance when ignoring large directories (#34400)Previous Releases
For information on prior major and minor releases, see their changelogs:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.