joao.dubas/ide
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

chore(deps): update dependency terraform to v1.10.0 #115

Merged
joao.dubas merged 1 commits from renovate/terraform-monorepo into main 2024-11-29 19:32:58 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2024-11-27 09:56:21 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
terraform minor 1.9.8 -> 1.10.0

Release Notes

hashicorp/terraform (terraform)

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:

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 Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [terraform](https://github.com/hashicorp/terraform) | minor | `1.9.8` -> `1.10.0` | --- ### Release Notes <details> <summary>hashicorp/terraform (terraform)</summary> ### [`v1.10.0`](https://github.com/hashicorp/terraform/releases/tag/v1.10.0) [Compare Source](https://github.com/hashicorp/terraform/compare/v1.9.8...v1.10.0) #### 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 ([#&#8203;35666](https://github.com/hashicorp/terraform/pull/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. ([#&#8203;35465](https://github.com/hashicorp/terraform/issues/35465)) - Sensitive marks could be incorrectly transferred to nested resource values, causing erroneous changes during a plan ([#&#8203;35501](https://github.com/hashicorp/terraform/issues/35501)) - Allow unknown `error_message` values to pass the core validate step, so variable validation can be completed later during plan ([#&#8203;35537](https://github.com/hashicorp/terraform/issues/35537)) - Unencoded slashes within GitHub module source refs were being truncated and incorrectly used as subdirectories in the request path ([#&#8203;35552](https://github.com/hashicorp/terraform/issues/35552)) - Terraform refresh-only plans with output only changes are now applyable. ([#&#8203;35812](https://github.com/hashicorp/terraform/issues/35812)) - Postconditions referencing `self` with many instances could encounter an error during evaluation ([#&#8203;35895](https://github.com/hashicorp/terraform/issues/35895)) - The `plantimestamp()` function would return an invalid date during validation ([#&#8203;35902](https://github.com/hashicorp/terraform/issues/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 ([#&#8203;35966](https://github.com/hashicorp/terraform/issues/35966)) - backend/cloud: Prefer KV tags, even when tags are defined as set ([#&#8203;35937](https://github.com/hashicorp/terraform/pull/35937)) - Simplify config generation (`plan -generate-config-out`) for string attributes that contain primitive types (e.g. numbers or booleans) ([#&#8203;35984](https://github.com/hashicorp/terraform/pull/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 ([#&#8203;36012](https://github.com/hashicorp/terraform/issues/36012)) - config: The evaluation of conditional expressions and for expression in HCL could lose marks with certain combinations of unknown values ([#&#8203;36017](https://github.com/hashicorp/terraform/issues/36017)) ENHANCEMENTS: - The `element` function now accepts negative indices ([#&#8203;35501](https://github.com/hashicorp/terraform/issues/35501)) - Import block validation has been improved to provide more useful errors and catch more invalid cases during `terraform validate` ([#&#8203;35543](https://github.com/hashicorp/terraform/issues/35543)) - Performance enhancements for resource evaluation, especially when large numbers of resource instances are involved ([#&#8203;35558](https://github.com/hashicorp/terraform/issues/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. ([#&#8203;35660](https://github.com/hashicorp/terraform/issues/35660)) - backend/cos: Add new auth for Tencent Cloud backend ([#&#8203;35888](https://github.com/hashicorp/terraform/pull/35888)) UPGRADE NOTES: - backend/s3: Removes deprecated attributes for assuming IAM role. Must use the `assume_role` block ([#&#8203;35721](https://github.com/hashicorp/terraform/issues/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. ([#&#8203;35661](https://github.com/hashicorp/terraform/issues/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. ([#&#8203;35850](https://github.com/hashicorp/terraform/issues/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](https://github.com/hashicorp/terraform/blob/v1.9/CHANGELOG.md) - [v1.8](https://github.com/hashicorp/terraform/blob/v1.8/CHANGELOG.md) - [v1.7](https://github.com/hashicorp/terraform/blob/v1.7/CHANGELOG.md) - [v1.6](https://github.com/hashicorp/terraform/blob/v1.6/CHANGELOG.md) - [v1.5](https://github.com/hashicorp/terraform/blob/v1.5/CHANGELOG.md) - [v1.4](https://github.com/hashicorp/terraform/blob/v1.4/CHANGELOG.md) - [v1.3](https://github.com/hashicorp/terraform/blob/v1.3/CHANGELOG.md) - [v1.2](https://github.com/hashicorp/terraform/blob/v1.2/CHANGELOG.md) - [v1.1](https://github.com/hashicorp/terraform/blob/v1.1/CHANGELOG.md) - [v1.0](https://github.com/hashicorp/terraform/blob/v1.0/CHANGELOG.md) - [v0.15](https://github.com/hashicorp/terraform/blob/v0.15/CHANGELOG.md) - [v0.14](https://github.com/hashicorp/terraform/blob/v0.14/CHANGELOG.md) - [v0.13](https://github.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md) - [v0.12](https://github.com/hashicorp/terraform/blob/v0.12/CHANGELOG.md) - [v0.11 and earlier](https://github.com/hashicorp/terraform/blob/v0.11/CHANGELOG.md) </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xMzMuMSIsInVwZGF0ZWRJblZlciI6IjM4LjEzMy4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate-bot added 1 commit 2024-11-27 09:56:22 +00:00
joao.dubas force-pushed renovate/terraform-monorepo from bba16a1d20 to 4d2235d75c 2024-11-29 18:18:52 +00:00 Compare
joao.dubas merged commit affdef24e3 into main 2024-11-29 19:32:58 +00:00
joao.dubas deleted branch renovate/terraform-monorepo 2024-11-29 19:32:58 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate-bot joao.dubas
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: joao.dubas/ide#115
No description provided.
Delete Branch "renovate/terraform-monorepo"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?