-
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 Terraform hashicorp/terraform to v1.9.2 #303
Open
staff-infrastructure-moj
wants to merge
1
commit into
main
Choose a base branch
from
renovate/hashicorp-terraform-1.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
staff-infrastructure-moj
requested review from
dms1981,
ASTRobinson and
kyphutruong
and removed request for
a team
July 18, 2024 02:17
staff-infrastructure-moj
temporarily deployed
to
development
July 18, 2024 02:17 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
July 25, 2024 02:17
4ac80c4
to
612aa0c
Compare
staff-infrastructure-moj
temporarily deployed
to
development
July 25, 2024 02:18 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
August 8, 2024 02:18
612aa0c
to
8889114
Compare
staff-infrastructure-moj
temporarily deployed
to
development
August 8, 2024 02:19 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
August 21, 2024 02:18
8889114
to
71b476f
Compare
staff-infrastructure-moj
temporarily deployed
to
development
August 21, 2024 02:18 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
September 19, 2024 02:25
71b476f
to
5fc8240
Compare
staff-infrastructure-moj
temporarily deployed
to
development
September 19, 2024 02:25 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
October 3, 2024 02:27
5fc8240
to
db1e4ff
Compare
staff-infrastructure-moj
temporarily deployed
to
development
October 3, 2024 02:27 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
October 17, 2024 02:27
db1e4ff
to
068da0d
Compare
staff-infrastructure-moj
temporarily deployed
to
development
October 17, 2024 02:27 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
November 15, 2024 02:30
068da0d
to
1f84761
Compare
staff-infrastructure-moj
had a problem deploying
to
development
November 15, 2024 02:30 — with
GitHub Actions
Failure
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
November 28, 2024 02:31
1f84761
to
1a32ea5
Compare
staff-infrastructure-moj
temporarily deployed
to
development
November 28, 2024 02:31 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
December 5, 2024 02:32
1a32ea5
to
0733229
Compare
staff-infrastructure-moj
had a problem deploying
to
development
December 5, 2024 02:32 — with
GitHub Actions
Failure
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
December 12, 2024 02:32
0733229
to
136d6c0
Compare
staff-infrastructure-moj
temporarily deployed
to
development
December 12, 2024 02:32 — with
GitHub Actions
Inactive
staff-infrastructure-moj
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
December 19, 2024 02:30
136d6c0
to
b535229
Compare
staff-infrastructure-moj
had a problem deploying
to
development
December 19, 2024 02:30 — with
GitHub Actions
Failure
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.1.3
->1.9.2
Release Notes
hashicorp/terraform (hashicorp/terraform)
v1.9.2
Compare Source
1.9.2 (July 10, 2024)
BUG FIXES:
count
andfor_each
meta attributes. (#35432)v1.9.1
Compare Source
1.9.1 (July 3, 2024)
UPGRADE NOTES:
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:
terraform test
: Removed additional erroneous error message when referencing attributes that don't exist. (#35408)import
blocks: Fix crash that occurs when incorrectly referencing theto
resource from theid
attribute. (#35420)v1.9.0
Compare Source
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:
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)templatestring
function allows rendering a template provided as a string. (#34968, #35224, #35285)resource
blocks. (#35088)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.
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)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)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)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)create_before_destroy
when replacing an instance, then applying with-refresh=false
would order the apply operations incorrectly (#35261)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.8.5
Compare Source
1.8.5 (June 5, 2024)
BUG FIXES:
terraform test
: Remove duplicate warning diagnostic when providing values for unknown variables in run blocks. (#35172)v1.8.4
Compare Source
1.8.4 (May 22, 2024)
BUG FIXES:
core
: Fix exponential slowdown in some cases when modules are usingdepends_on
. (#35157)import
blocks: Fix bug where resources with nested, computed, and optionalid
attributes would fail to generate configuration. (#35220)golang.org/x/net
release, which addressed CVE-2023-45288 (#35165)v1.8.3
Compare Source
1.8.3 (May 8, 2024)
BUG FIXES:
terraform test
: Providers configured within an overridden module could panic. (#35110)core
: Fix crash when a provider incorrectly plans a nested object when the configuration isnull
(#35090)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)v1.6.1
Compare Source
1.6.1 (October 10, 2023)
ENHANCEMENTS:
skip_requesting_account_id
argument supports AWS API implementations that do not have the IAM, STS, or metadata API. (#34002)BUG FIXES:
GIT_SSH_COMMAND
is now preserved again when fetching modules from git source addresses. [GH-34045]TF_WORKSPACE
environment variable works with thecloud
block again; it can specify a workspace when none is configured, or select an active workspace when the config specifiestags
. [GH-34012]kms_key_id
argument will no longer fail validation. (#33993)v1.6.0
Compare Source
1.6.0 (October 4, 2023)
UPGRADE NOTES:
hashicorp/aws
provider: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_keys
are all now deprecated in favor of the nested equivalents. (#30495)endpoints
. The top-level argumentsdynamodb_endpoint
,iam_endpoint
,endpoint
(fir S3), andsts_endpoint
are now deprecated in favor of the nested equivalents. (#30492)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)shared_credentials_file
argument is deprecated in favor of the pluralshared_credentials_files
.force_path_style
argument is deprecated in favor ofuse_path_style
for consistency with the AWS SDK. (#30491)NEW FEATURES:
terraform test
: Theterraform test
command 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.hcl
files, containing a series ofrun
blocks. Eachrun
block 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
import
blockid
field 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
-out
option, viewed usingterraform show
, and applied usingterraform apply
with 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.
core: Provider schemas can now be cached globally for compatible providers, allowing them to be reused throughout core without requesting them for each new provider instance. This can significantly reduce memory usage when there are many instances of the same provider in a single configuration (#33482)
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
try
andcan
functions can now return more precise and consistent results when faced with unknown arguments (#33758)terraform show -json
: Now includeserrored
property, 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/aws
provider capabilities:assume_role_with_web_identity
nested block for assuming a role with dynamic credentials such as a JSON Web Token. (#31244)AWS_CONFIG_FILE
andAWS_SHARED_CREDENTIALS_FILE
. (#30493)shared_config_files
andshared_credentials_files
arguments for specifying credential and configuration files as part of the backend configuration. (#30493)custom_ca_bundle
argument and support for the corresponding AWS environment variable,AWS_CA_BUNDLE
, for providing custom root and intermediate certificates. (#33689)ec2_metadata_service_endpoint
andec2_metadata_service_endpoint_mode
arguments and support for the corresponding AWS environment variables,AWS_EC2_METADATA_SERVICE_ENDPOINT
andAWS_EC2_METADATA_SERVICE_ENDPOINT_MODE
for setting the EC2 metadata service (IMDS) endpoint. The environment variableAWS_METADATA_URL
is also supported for compatibility with the AWS provider, but is deprecated. (#30444)http_proxy
,insecure
,use_fips_endpoint
, anduse_dualstack_endpoint
arguments and support for the corresponding environment variables,HTTP_PROXY
andHTTPS_PROXY
, which enable custom HTTP proxy configurations and the resolution of AWS endpoints with extended capabilities. (#30496)sts_region
argument to use an alternative region for STS operations. (#33693)retry_mode
argument and support for the correspondingAWS_RETRY_MODE
environment variable to configure how retries are attempted. (#33692)allowed_account_ids
andforbidden_account_ids
arguments 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:
terraform
built-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_state
blocks 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)Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.5.7
Compare Source
1.5.7 (September 7, 2023)
BUG FIXES:
terraform init
: Terraform will no longer allow downloading remote modules to invalid paths. (#33745)terraform_remote_state
: prevent future possible incompatibility with states which include unknowncheck
block result kinds. (#33818)v1.5.6
Compare Source
1.5.6 (August 23, 2023)
BUG FIXES:
v1.5.5
Compare Source
1.5.5 (August 9, 2023)
terraform init
: Fix crash when using invalid configuration in backend blocks. (#33628)v1.5.4
Compare Source
1.5.4 (July 26, 2023)
BUG FIXES:
check
blocks: Fixes crash when nested data sources are within configuration targeted by the terraform import command. (#33578)check
blocks: Check blocks now operate in line with other checkable objects by also executing during import operations. (#33578)v1.5.3
Compare Source
1.5.3 (July 12, 2023)
BUG FIXES:
consul CAS failed with transaction errors
no longer shows an error instance memory address, but an actual error message. (#33108)v1.5.2
Compare Source
1.5.2 (June 28, 2023)
BUG FIXES:
import
blocks with the sameid
string no longer result in a validation error (#33434)v1.5.1
Compare Source
1.5.1 (June 21, 2023)
BUG FIXES:
v1.5.0
Compare Source
1.5.0 (June 12, 2023)
NEW FEATURES:
check
blocks for validating infrastructure: Module and configuration authors can now write independent check blocks within their configuration to validate assertions about their infrastructure.The new independent
check
blocks must specify at least oneassert
block, but possibly many, each one with acondition
expression and anerror_message
expression matching the existing Custom Condition Checks.Additionally, check blocks can optionally load a scoped data source. Scoped data sources match the existing data sources with the exception that they can only be referenced from within their check block.
Unlike the existing
precondition
andpostcondition
blocks, Terraform will not halt execution should the scoped data block fail or error or if any of the assertions fail.This allows practitioners to continually validate the state of their infrastructure outside the usual lifecycle management cycle.
import
blocks for importing infrastructure: Root module authors can now use theimport
block to declare their intent that Terraform adopt an existing resource.Import is now a configuration-driven, plannable action, and is processed as part of a normal plan. Running
terraform plan
will show a summary of the resources that Terraform has planned to import, along with any other plan changes.The existing
terraform import
CLI command has not been modified.This is an early version of the
import
block feature, for which we are actively seeking user feedback to shape future development. Theimport
block currently does not support interpolation in theid
field, which must be a string.Generating configuration for imported resources: in conjunction with the
import
block, this feature enables easy templating of configuration when importing existing resources into Terraform. A new flag-generate-config-out=PATH
is added toterraform plan
. When this flag is set, Terraform will generate HCL configuration for any resource included in animport
block that does not already have associated configuration, and write it to a new file atPATH
. Before applying, review the generated configuration and edit it as necessary.Adds a new
plantimestamp
function that returns the timestamp at plan time. This is similar to thetimestamp
function which returns the timestamp at apply time (#32980).Adds a new
strcontains
function that checks whether a given string contains a given substring. (#33069)UPGRADE NOTES:
This is the last version of Terraform for which macOS 10.13 High Sierra or 10.14 Mojave are officially supported. Future Terraform versions may not function correctly on these older versions of macOS.
This is the last version of Terraform for which Windows 7, 8, Server 2008, and Server 2012 are supported by Terraform's main implementation language, Go. We already ended explicit support for versions earlier than Windows 10 in Terraform v0.15.0, but future Terraform versions may malfunction in more significant ways on these older Windows versions.
On Linux (and some other non-macOS Unix platforms we don't officially support), Terraform will now notice the
trust-ad
option in/etc/resolv.conf
and, if set, will set the "authentic data" option in outgoing DNS requests in order to better match the behavior of the GNU libc resolver.Terraform does not pay any attention to the corresponding option in responses, but some DNSSEC-aware recursive resolvers return different responses when the request option isn't set. This should therefore avoid some potential situations where a DNS request from Terraform might get a different response than a similar request from other software on your system.
ENHANCEMENTS:
pg
backend: Now supports thePG_CONN_STR
,PG_SCHEMA_NAME
,PG_SKIP_SCHEMA_CREATION
,PG_SKIP_TABLE_CREATION
andPG_SKIP_INDEX_CREATION
environment variables. (#33045)BUG FIXES:
terraform init
: Fixed crash with invalid blank module name. (#32781)moved
blocks: Fixed a typo in the error message that Terraform raises when you use-target
to exclude an object that has been moved. (#33149)Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.4.7
Compare Source
1.4.7 (September 13, 2023)
BUG FIXES:
terraform_remote_state
: fix incompatibility with states produced by Terraform 1.5 or later which includecheck
block results. (#33814)v1.4.6
Compare Source
1.4.6 (April 26, 2023)
BUG FIXES
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 Renovate Bot.