generated from dxw/terraform-template
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency hashicorp/terraform to v1.8.2 #31
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9e7d39f
to
2a81834
Compare
2a81834
to
1478119
Compare
1478119
to
e0b4b56
Compare
e0b4b56
to
a0a67ad
Compare
a0a67ad
to
9d8e292
Compare
9d8e292
to
6ae2a44
Compare
6ae2a44
to
b8a726a
Compare
b8a726a
to
e545f95
Compare
e545f95
to
0dde83b
Compare
0dde83b
to
5120f0a
Compare
5120f0a
to
1f2bc89
Compare
1f2bc89
to
69f382e
Compare
69f382e
to
eed2349
Compare
Stretch96
approved these changes
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.1
->1.8.2
Release Notes
hashicorp/terraform (hashicorp/terraform)
v1.8.2
Compare Source
1.8.2 (April 24, 2024)
BUG FIXES:
terraform apply
: Prevent panic when a provider erroneously provides unknown values. (#35048)terraform plan
: Replace panic with error message when self-referencing resources and data sources from thecount
andfor_each
meta attributes. (#35047)terraform test
: RestoreTF_ENV_*
variables being made available to testing modules. (#35014)terraform test
: Prevent crash when referencing local variables within overridden modules. (#35030)ENHANCEMENTS:
OTHER CHANGES:
cloud
block and environment variables likeTF_CLOUD_ORGANIZATION
remain unchanged. (#35050)NOTE:
Starting with this release, we are including a copy of our license file in all packaged versions of our releases, such as the release .zip files. If you are consuming these files directly and would prefer to extract the one terraform file instead of extracting everything, you need to add an extra argument specifying the file to extract, like this:
v1.8.1
Compare Source
1.8.1 (April 17, 2024)
BUG FIXES:
moved
block: Fix crash when move targets a module which no longer exists. (#34986)import
block: Fix crash when generating configuration for resources with complex sensitive attributes. (#34996)v1.8.0
Compare Source
1.8.0 (April 10, 2024)
If you are upgrading from Terraform v1.7 or earlier, please refer to
the Terraform v1.8 Upgrade Guide.
NEW FEATURES:
Providers can now offer functions which can be used from within the Terraform configuration language.
The syntax for calling a provider-contributed function is
provider::provider_name::function_name()
. (#34394)Providers can now transfer the ownership of a remote object between resources of different types, for situations where there are two different resource types that represent the same remote object type.
This extends the
moved
block behavior to support moving between two resources of different types only if the provider for the target resource type declares that it can convert from the source resource type. Refer to provider documentation for details on which pairs of resource types are supported.New
issensitive
function returns true if the given value is marked as sensitive.ENHANCEMENTS:
terraform test
: File-level variables can now refer to global variables. (#34699)When generating configuration based on
import
blocks, Terraform will detect strings that contain valid JSON syntax and generate them as calls to thejsonencode
function, rather than generating a single string. This is primarily motivated by readability, but might also be useful if you need to replace part of the literal value with an expression as you generalize your module beyond the one example used for importing.terraform plan
now uses a different presentation for describing changes to lists where the old and new lists have the same length. It now compares the elements with correlated indices and shows a separate diff for each one, rather than trying to show a diff for the list as a whole. The behavior is unchanged for lists of different lengths.terraform providers lock
accepts a new boolean option-enable-plugin-cache
. If specified, and if a global plugin cache is configured, Terraform will use the cache in the provider lock process. (#34632)built-in "terraform" provider: new
decode_tfvars
,encode_tfvars
, andencode_expr
functions, for unusual situations where it's helpful to manually generate or read from Terraform's "tfvars" format. (#34718)terraform show
's JSON rendering of a plan now includes two explicit flags"applyable"
and"complete"
, which both summarize characteristics of a plan that were previously only inferrable by consumers replicating some of Terraform Core's own logic. (#34642)"applyable"
means that it makes sense for a wrapping automation to offer to apply this plan."complete"
means that applying this plan is expected to achieve convergence between desired and actual state. If this flag is present and set tofalse
then wrapping automations should ideally encourage an operator to run another plan/apply round to continue making progress toward convergence.BUG FIXES:
iterator
argument within a dynamic block. (#34751)Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.7.5
Compare Source
1.7.5 (March 13, 2024)
BUG FIXES:
v1.7.4
Compare Source
1.7.4 (February 21, 2024)
BUG FIXES:
terraform test
: Fix automatic loading of variable files within the test directory onwindows
platforms. (#34666)v1.7.3
Compare Source
1.7.3 (February 7, 2024)
BUG FIXES:
terraform test
: Fix crash when dynamic-typed attributes are not assigned values in mocks. (#34610)import
: Throw helpful error message if an import block is configured with an empty ID (34625)v1.7.2
Compare Source
1.7.2 (January 31, 2024)
BUG FIXES:
env:
. (#34511)ENHANCEMENTS:
terraform fmt
: Terraform mock data files (.tfmock.hcl
) will now be included when executing the format command. (#34580)v1.7.1
Compare Source
1.7.1 (January 24, 2024)
BUG FIXES:
terraform test
: Fix crash when referencing variables or functions within the file levelvariables
block. (#34531)terraform test
: Fix crash whenoverride_module
block was missing theoutputs
attribute. (#34563)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:
v1.6.6
Compare Source
1.6.6 (December 13, 2023)
BUG FIXES:
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)v1.6.5
Compare Source
1.6.5 (November 29, 2023)
BUG FIXES:
v1.6.4
Compare Source
1.6.4 (November 15, 2023)
ENHANCEMENTS:
endpoints.sso
to allow overriding the AWS SSO API endpoint. (#34195)BUG FIXES:
terraform test
: Fix bug preventing passing sensitive output values from previous run blocks as inputs to future run blocks. (#34190)https_proxy
andno_proxy
parameters to allow fully specifying proxy configuration (#34243)v1.6.3
Compare Source
1.6.3 (November 1, 2023)
ENHANCEMENTS:
skip_s3_checksum
to allow users to disable checksum on S3 uploads for compatibility with "S3-compatible" APIs. (#34127)v1.6.2
Compare Source
1.6.2 (October 18, 2023)
BUG FIXES
terraform test
: Fix performance issues when using provisioners within configs being tested. (#34026)terraform test
: Only process and parse relevant variables for each run block. (#34072)-reconfigure
during eachinit
when config was not decoded correctly (#34108)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.