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 terraform hashicorp/terraform to v1.9.5 - autoclosed #17

Closed
wants to merge 1 commit into from

Conversation

dc-tec
Copy link
Owner

@dc-tec dc-tec commented Jun 29, 2024

This PR contains the following updates:

Package Type Update Change
hashicorp/terraform required_version minor 1.8.5 -> 1.9.5

Release Notes

hashicorp/terraform (hashicorp/terraform)

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)

v1.9.2

Compare Source

1.9.2 (July 10, 2024)

BUG FIXES:

  • core: Fix panic when self-referencing direct instances from count and for_each meta attributes. (#​35432)

v1.9.1

Compare Source

1.9.1 (July 3, 2024)

UPGRADE NOTES:

  • Library used by Terraform (hashicorp/go-getter) for installing/updating modules was upgraded from v1.7.4 to v1.7.5. This addresses CVE-2024-6257. This change may have a negative effect on performance of terraform init or terraform get in case of larger git repositories. Please do file an issue if you find the performance difference noticable. (#​35376)

BUG FIXES:

  • terraform test: Removed additional erroneous error message when referencing attributes that don't exist. (#​35408)
  • import blocks: Fix crash that occurs when incorrectly referencing the to resource from the id attribute. (#​35420)

v1.9.0

Compare Source

1.9.0 (June 26, 2024)

If you are upgrading from an earlier minor release, please refer to the Terraform v1.9 Upgrade Guide.

NEW FEATURES:

  • Input variable validation rules can refer to other objects: Previously input variable validation rules could refer only to the variable being validated. Now they are general expressions, similar to those elsewhere in a module, which can refer to other input variables and to other objects such as data resources.
  • templatestring function: a new built-in function which is similar to templatefile but designed to render templates obtained dynamically, such as from a data resource result.

ENHANCEMENTS:

  • terraform plan: Improved presentation of OPA and Sentinel policy evaluations in HCP Terraform remote runs, for logical separation.
  • terraform init now accepts a -json option. If specified, enables the machine readable JSON output. (#​34886)
  • terraform test: Test runs can now pass sensitive values to input variables while preserving their dynamic sensitivity. Previously sensitivity would be preserved only for variables statically declared as being sensitive, using sensitive = true. (#​35021)
  • config: Input variable validation rules can now refer to other objects in the same module. (#​34955)
  • config: templatestring function allows rendering a template provided as a string. (#​34968, #​35224, #​35285)
  • core: Performance improvement during graph building for configurations with an extremely large number of resource blocks. (#​35088)
  • built-in terraform provider: Allows moved block refactoring from the hashicorp/null provider null_resource resource type to the terraform_data resource type. (#​35163)
  • terraform output with cloud block: Terraform no longer suggests that data loss could occur when outputs are not available. (#​35143)
  • terraform console: Now has basic support for multi-line input in interactive mode. (#​34822)
    If an entered line contains opening parentheses/etc that are not closed, Terraform will await another line of input to complete the expression. This initial implementation is primarily intended to support pasting in multi-line expressions from elsewhere, rather than for manual multi-line editing, so the interactive editing support is currently limited.
  • cli: Reduced copying of state to improve performance with large numbers of resources. (#​35164)
  • removed blocks can now declare destroy-time provisioners which will be executed when the associated resource instances are destroyed. (#​35230)

BUG FIXES:

  • remote-exec provisioner: Each remote connection will now be closed immediately after use. (#​34137)
  • backend/s3: Fixed the digest value displayed for DynamoDB/S3 state checksum mismatches. (#​34387)
  • terraform test: Fix bug in which non-Hashicorp providers required by testing modules and initialised within the test files were assigned incorrect registry addresses. (#​35161)
  • config: The templatefile function no longer returns a "panic" error if the template file path is marked as sensitive. Instead, the template rendering result is also marked as sensitive. (#​35180)
  • config: import blocks which referenced resources in non-existent modules were silently ignored when they should have raised an error (#​35330)
  • terraform init: When selecting a version for a provider that has both positive and negative version constraints for the same prerelease -- e.g. 1.2.0-beta.1, !1.2.0-beta.1 -- the negative constraint will now overrule the positive, for consistency with how negative constraints are handled otherwise. Previously Terraform would incorrectly treat the positive as overriding the negative if the specified version was a prerelease. (#​35181)
  • import: import blocks could block a destroy operation if the target resource was already deleted (#​35272)
  • cli: plan output was missing blocks which were entirely unknown (#​35271)
  • cli: fix crash when running providers mirror with an incomplete lock file (#​35322)
  • core: Changing create_before_destroy when replacing an instance, then applying with -refresh=false would order the apply operations incorrectly (#​35261)
  • core: Resource addresses that start with the optional resource. prefix will now be correctly parsed when used as an address target. (#​35333)

UPGRADE NOTES:

  • terraform test: It is no longer valid to specify version constraints within provider blocks within .tftest.hcl files. Instead, version constraints must be supplied within the main configuration where the provider is in use.
  • import: Invalid import blocks pointing to nonexistent modules were mistakenly ignored in prior versions. These will need to be fixed or removed in v1.9.
Previous Releases

For information on prior major and minor releases, see 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.

@dc-tec dc-tec force-pushed the renovate/hashicorp-terraform-1.x branch from 6db07d9 to fb8f7c0 Compare July 6, 2024 01:42
@dc-tec dc-tec changed the title chore(deps): update terraform hashicorp/terraform to v1.9.0 chore(deps): update terraform hashicorp/terraform to v1.9.1 Jul 6, 2024
@dc-tec dc-tec force-pushed the renovate/hashicorp-terraform-1.x branch from fb8f7c0 to 6afa441 Compare July 13, 2024 01:45
@dc-tec dc-tec changed the title chore(deps): update terraform hashicorp/terraform to v1.9.1 chore(deps): update terraform hashicorp/terraform to v1.9.2 Jul 13, 2024
@dc-tec dc-tec force-pushed the renovate/hashicorp-terraform-1.x branch from 6afa441 to 301ce14 Compare July 27, 2024 01:45
@dc-tec dc-tec changed the title chore(deps): update terraform hashicorp/terraform to v1.9.2 chore(deps): update terraform hashicorp/terraform to v1.9.3 Jul 27, 2024
@dc-tec dc-tec force-pushed the renovate/hashicorp-terraform-1.x branch from 301ce14 to 96a7d4c Compare August 10, 2024 01:49
@dc-tec dc-tec changed the title chore(deps): update terraform hashicorp/terraform to v1.9.3 chore(deps): update terraform hashicorp/terraform to v1.9.4 Aug 10, 2024
@dc-tec dc-tec force-pushed the renovate/hashicorp-terraform-1.x branch from 96a7d4c to 8a69454 Compare August 21, 2024 01:48
@dc-tec dc-tec changed the title chore(deps): update terraform hashicorp/terraform to v1.9.4 chore(deps): update terraform hashicorp/terraform to v1.9.5 Aug 21, 2024
@dc-tec dc-tec changed the title chore(deps): update terraform hashicorp/terraform to v1.9.5 chore(deps): update terraform hashicorp/terraform to v1.9.5 - autoclosed Aug 24, 2024
@dc-tec dc-tec closed this Aug 24, 2024
@dc-tec dc-tec deleted the renovate/hashicorp-terraform-1.x branch August 24, 2024 01:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants