Skip to content
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.10.3 #60

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 28, 2024

This PR contains the following updates:

Package Type Update Change
hashicorp/terraform minor 1.9.2 -> 1.10.3
hashicorp/terraform (source) docker minor 1.9.2 -> 1.10.3

Release Notes

hashicorp/terraform (hashicorp/terraform)

v1.10.3

Compare Source

1.10.3 (December 18, 2024)

BUG FIXES:

  • Terraform could panic when encountering an error during plan encoding (#​36212)

v1.10.2

Compare Source

1.10.2 (December 11, 2024)

BUG FIXES:

  • cli: variables in an auto-loaded tfvars file which were overridden during plan incorrectly show as changed during apply [GH-36180]

v1.10.1

Compare Source

1.10.1 (December 4, 2024)

BUG FIXES:

  • cli: Complex variables values set via environment variables were parsed incorrectly during apply (#​36121)
  • config: templatefile would panic if given and entirely unknown map of variables (#​36118)
  • config: templatefile would panic if the variables map contains marked values (#​36127)
  • config: Remove constraint that an expanded resource block must only be used in conjunction with imports using for_each (#​36119)
  • backend/s3: Lock files could not be written to buckets with object locking enabled (#​36120)

v1.10.0

Compare Source

1.10.0 (November 27, 2024)

NEW FEATURES:

  • Ephemeral resources: Ephemeral resources are read anew during each phase of Terraform evaluation, and cannot be persisted to state storage. Ephemeral resources always produce ephemeral values.
  • Ephemeral values: Input variables and outputs can now be defined as ephemeral. Ephemeral values may only be used in certain contexts in Terraform configuration, and are not persisted to the plan or state files.
    • ephemeralasnull function: a function takes a value of any type and returns a similar value of the same type with any ephemeral values replaced with non-ephemeral null values and all non-ephemeral values preserved.

BUG FIXES:

  • The secret_suffix in the kubernetes backend now includes validation to prevent errors when the secret_suffix ends with a number (#​35666).
  • The error message for an invalid default value for an input variable now indicates when the problem is with a nested value in a complex data type. (#​35465)
  • Sensitive marks could be incorrectly transferred to nested resource values, causing erroneous changes during a plan (#​35501)
  • Allow unknown error_message values to pass the core validate step, so variable validation can be completed later during plan
    (#​35537)
  • Unencoded slashes within GitHub module source refs were being truncated and incorrectly used as subdirectories in the request path (#​35552)
  • Terraform refresh-only plans with output only changes are now applyable. (#​35812)
  • Postconditions referencing self with many instances could encounter an error during evaluation (#​35895)
  • The plantimestamp() function would return an invalid date during validation (#​35902)
  • Updates to resources which were forced to use create_before_destroy could lose that flag in the state temporarily and cause cycles if immediately removed from the configuration (#​35966)
  • backend/cloud: Prefer KV tags, even when tags are defined as set (#​35937)
  • Simplify config generation (plan -generate-config-out) for string attributes that contain primitive types (e.g. numbers or booleans) (#​35984)
  • config: issensitive could incorrectly assert that an unknown value was not sensitive during plan, but later became sensitive during apply, causing failures where changes did not match the planned result (#​36012)
  • config: The evaluation of conditional expressions and for expression in HCL could lose marks with certain combinations of unknown values (#​36017)

ENHANCEMENTS:

  • The element function now accepts negative indices (#​35501)
  • Import block validation has been improved to provide more useful errors and catch more invalid cases during terraform validate (#​35543)
  • Performance enhancements for resource evaluation, especially when large numbers of resource instances are involved (#​35558)
  • The plan, apply, and refresh commands now produce a deprecated warning when using the -state flag. Instead use the path attribute within the local backend to modify the state file. (#​35660)
  • backend/cos: Add new auth for Tencent Cloud backend (#​35888)

UPGRADE NOTES:

  • backend/s3: Removes deprecated attributes for assuming IAM role. Must use the assume_role block (#​35721)
  • backend/s3: The s3 backend now supports S3 native state locking. When used with DynamoDB-based locking, locks will be acquired from both sources. In a future minor release of Terraform the DynamoDB locking mechanism and associated arguments will be deprecated. (#​35661)
  • moved: Moved blocks now respect reserved keywords when parsing resource addresses. Configurations that reference resources with type names that match top level blocks and keywords from moved blocks will need to prepend the resource. identifier to these references. (#​35850)
  • config: In order to ensure consistency in results from HCL conditional expressions, marks must be combined from all values within the expression to avoid losing mark information. This typically improves accuracy when validating configuration, but users may see sensitive results where they were lost previously.

Previous Releases

For information on prior major and minor releases, refer to their changelogs:

v1.9.8

Compare Source

1.9.8 (October 16, 2024)

BUG FIXES:

  • init: Highlight missing subdirectories of registry modules in error message (#​35848)
  • init: Prevent crash when loading provider_meta blocks with invalid names (#​35842)
  • config generation: Escape all invalid syntax in generate map keys with quotes (#​35837)
  • plan: also validate provider requirements from state (#​35864)

v1.9.7

Compare Source

1.9.7 (October 2, 2024)

BUG FIXES:

  • config generation: escape map keys with whitespaces (#​35754)

v1.9.6

Compare Source

1.9.6 (September 18, 2024)

BUG FIXES:

  • plan renderer: Render complete changes within unknown nested blocks. (#​35644)
  • plan renderer: Fix crash when attempting to render unknown nested blocks that contain attributes forcing resource replacement. (#​35644)
  • plan renderer: Fix crash when rendering a plan that contains null attributes being update to unknown values. (#​35709)

v1.9.5

Compare Source

1.9.5 (August 20, 2024)

ENHANCEMENTS:

  • cloud: The cloud block can now interact with workspaces that have HCP resource IDs. (#​35495)

BUG FIXES:

  • core: removed blocks with provisioners were not executed when the resource was in a nested module. (#​35611)

v1.9.4

Compare Source

1.9.4 (August 7, 2024)

BUG FIXES:

  • core: Unneeded variable validations were being executed during a destroy plan, which could cause plans starting with incomplete state to fail. (#​35511)
  • init: Don't crash when discovering invalid syntax in duplicate required_providers blocks. (#​35533)

v1.9.3

Compare Source

1.9.3 (July 24, 2024)

ENHANCEMENTS:

  • Terraform now returns a more specific error message in the awkward situation where an input variable validation rule is known to have failed (condition returned false) but the error message is derived from an unknown value. (#​35400)

BUG FIXES:

  • core: Terraform no longer performs an unnecessary refresh when removing an instance targeted by a removed block. (#​35458)
  • config generation: Fix validation error when using nested computed or deprecated attributes. (#​35484)
  • Updated to newer github.com/hashicorp/go-retryablehttp version, addressing CVE-2024-6104, and bringing in updates for several indirect dependencies. (#​35473)
  • Moved to building with Go 1.22.5, which addresses CVE-2024-24791 and several other non-security bugs. (#​35494)

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from 17825e4 to 6b85f4a Compare September 18, 2024 10:56
@renovate renovate bot changed the title Update dependency hashicorp/terraform to v1.9.5 Update dependency hashicorp/terraform to v1.9.6 Sep 18, 2024
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from 6b85f4a to 42ec8e6 Compare October 2, 2024 18:33
@renovate renovate bot changed the title Update dependency hashicorp/terraform to v1.9.6 Update terraform monorepo Oct 2, 2024
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from 42ec8e6 to d8bcd31 Compare October 2, 2024 22:28
@renovate renovate bot changed the title Update terraform monorepo Update dependency hashicorp/terraform to v1.9.7 Oct 2, 2024
@renovate renovate bot changed the title Update dependency hashicorp/terraform to v1.9.7 Update terraform monorepo Oct 16, 2024
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from d8bcd31 to 788e3a5 Compare October 16, 2024 15:20
@renovate renovate bot changed the title Update terraform monorepo Update dependency hashicorp/terraform to v1.9.8 Oct 16, 2024
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from 788e3a5 to 294a5b4 Compare October 16, 2024 19:27
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from 294a5b4 to 6a3af02 Compare November 27, 2024 11:44
@renovate renovate bot changed the title Update dependency hashicorp/terraform to v1.9.8 Update dependency hashicorp/terraform to v1.10.0 Nov 27, 2024
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from 6a3af02 to e7133f4 Compare December 4, 2024 13:42
@renovate renovate bot changed the title Update dependency hashicorp/terraform to v1.10.0 Update dependency hashicorp/terraform to v1.10.1 Dec 4, 2024
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from e7133f4 to 3cf663c Compare December 11, 2024 13:20
@renovate renovate bot changed the title Update dependency hashicorp/terraform to v1.10.1 Update terraform monorepo Dec 11, 2024
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from 3cf663c to 6485599 Compare December 11, 2024 16:13
@renovate renovate bot changed the title Update terraform monorepo Update dependency hashicorp/terraform to v1.10.2 Dec 11, 2024
@renovate renovate bot force-pushed the renovate/terraform-monorepo branch from 6485599 to 5d01306 Compare December 18, 2024 15:55
@renovate renovate bot changed the title Update dependency hashicorp/terraform to v1.10.2 Update dependency hashicorp/terraform to v1.10.3 Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants