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

chore(deps): update dependency hashicorp/terraform to v1.8.4 #34

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 21, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
hashicorp/terraform minor 1.7.3 -> 1.8.4

Release Notes

hashicorp/terraform (hashicorp/terraform)

v1.8.4

Compare Source

1.8.4 (May 22, 2024)

BUG FIXES:

  • core: Fix exponential slowdown in some cases when modules are using depends_on. (#​35157)
  • import blocks: Fix bug where resources with nested, computed, and optional id attributes would fail to generate configuration. (#​35220)
  • Updated to new 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 is null (#​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 the count and for_each meta attributes. (#​35047)
  • terraform test: Restore TF_ENV_* variables being made available to testing modules. (#​35014)
  • terraform test: Prevent crash when referencing local variables within overridden modules. (#​35030)

ENHANCEMENTS:

  • Improved performance by removing unneeded additional computation for a disabled experimental feature. (#​35066)

OTHER CHANGES:

  • Update all references to Terraform Cloud to refer to HCP Terraform, the service's new name. This only affects display text; the cloud block and environment variables like TF_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:

unzip terraform_1.8.2_linux_amd64.zip terraform

v1.8.1

Compare Source

1.8.1 (April 17, 2024)

BUG FIXES:

  • Fix crash in terraform plan when referencing a module output that does not exist within the try(...) function. (#​34985)
  • Fix crash in terraform apply when referencing a module with no planned changes. (#​34985)
  • 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)
  • Plan renderer: Correctly render strings that begin with JSON compatible text but don't end with it. (#​34959)

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 the jsonencode 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, and encode_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 to false then wrapping automations should ideally encourage an operator to run another plan/apply round to continue making progress toward convergence.

BUG FIXES:

  • core: Sensitive values will now be tracked more accurately in state and plans, preventing unexpected updates with no apparent changes. (#​34567)
  • core: Fix incorrect error message when using in invalid iterator argument within a dynamic block. (#​34751)
  • core: Fixed edge-case bug that could cause loss of floating point precision when round-tripping due to incorrectly using a MessagePack integer to represent a large non-integral number. (#​24576)
  • config: Converting from an unknown map value to an object type now correctly handles the situation where the map element type disagrees with an optional attribute of the target type, since when a map value is unknown we don't yet know which keys it has and thus cannot predict what subset of the elements will get converted as attributes in the resulting object. (#​34756)
  • cloud: Fixed unparsed color codes in policy failure error messages. (#​34473)

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:

  • backend/s3: When using s3 backend and encountering a network issue, the retry code would fail with "failed to rewind transport stream for retry". Now the retry should be successful. (#​34796)

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 on windows platforms. (#​34666)
  • plan renderer: Very large numbers (> 2^63) will no longer be truncated in the human-readable plan. (#​34702)

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.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency hashicorp/terraform to v1.7.4 chore(deps): update dependency hashicorp/terraform to v1.7.5 Mar 14, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-terraform-1.x branch from 1ce9f69 to 0914ea4 Compare March 14, 2024 00:59
@renovate renovate bot changed the title chore(deps): update dependency hashicorp/terraform to v1.7.5 chore(deps): update dependency hashicorp/terraform to v1.8.0 Apr 10, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-terraform-1.x branch 2 times, most recently from 4480130 to fca15a5 Compare April 17, 2024 10:55
@renovate renovate bot changed the title chore(deps): update dependency hashicorp/terraform to v1.8.0 chore(deps): update dependency hashicorp/terraform to v1.8.1 Apr 17, 2024
@renovate renovate bot changed the title chore(deps): update dependency hashicorp/terraform to v1.8.1 chore(deps): update dependency hashicorp/terraform to v1.8.2 Apr 24, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-terraform-1.x branch from fca15a5 to 7d86bec Compare April 24, 2024 12:22
@renovate renovate bot changed the title chore(deps): update dependency hashicorp/terraform to v1.8.2 chore(deps): update dependency hashicorp/terraform to v1.8.3 May 8, 2024
@renovate renovate bot force-pushed the renovate/hashicorp-terraform-1.x branch from 7d86bec to e24fc04 Compare May 8, 2024 11:26
@renovate renovate bot force-pushed the renovate/hashicorp-terraform-1.x branch from e24fc04 to 40e6c9e Compare May 22, 2024 19:41
@renovate renovate bot changed the title chore(deps): update dependency hashicorp/terraform to v1.8.3 chore(deps): update dependency hashicorp/terraform to v1.8.4 May 22, 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.

None yet

0 participants