chore(deps): update dependency hashicorp/terraform to v1.5.0 in .circleci/config.yml #3514
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.6
->1.5.0
Release Notes
hashicorp/terraform
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:
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.