chore(deps): update dependency hashicorp/terraform to v1.6.6 in dockerfile #241
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.4.0
->1.6.6
Release Notes
hashicorp/terraform (hashicorp/terraform)
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
terraform show -json
output. (#33059)# forces replacement
suffix. (#33065)v1.4.5
Compare Source
1.4.5 (April 12, 2023)
terraform_data
to fail when being replaced withcreate_before_destroy
(#32988)v1.4.4
Compare Source
1.4.4 (March 30, 2023)
Due to an incident while migrating build systems for the 1.4.3 release where
CGO_ENABLED=0
was not set, we are rebuilding that version as 1.4.4 with theflag set. No other changes have been made between 1.4.3 and 1.4.4.
v1.4.3
Compare Source
1.4.3 (March 30, 2023)
BUG FIXES:
v1.4.2
Compare Source
1.4.2 (March 16, 2023)
BUG FIXES:
setproduct
caused Terraform to crash (#32860)v1.4.1
Compare Source
1.4.1 (March 15, 2023)
BUG FIXES:
depends_on
attribute set, while still preventing thedepends_on
attribute itself from being overridden. (#32796)terraform providers mirror
: when a dependency lock file is present, mirror the resolved providers versions, not the latest available based on configuration. (#32749)TF_CLI_CONFIG_FILE
(#32846)Configuration
📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.