github-actions[bot]
commented
3 months ago No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
This PR contains the following updates:
1.8.5->1.9.01.8.5->1.9.0Release Notes
hashicorp/terraform (hashicorp/terraform)
### [`v1.9.0`](https://togithub.com/hashicorp/terraform/releases/tag/v1.9.0) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v1.8.5...v1.9.0) ##### 1.9.0 (June 26, 2024) If you are upgrading from an earlier minor release, please refer to [the Terraform v1.9 Upgrade Guide](https://developer.hashicorp.com/terraform/language/v1.9.x/upgrade-guides). 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](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/pull/35021)) - config: Input variable validation rules can now refer to other objects in the same module. ([#34955](https://togithub.com/hashicorp/terraform/pull/34955)) - config: `templatestring` function allows rendering a template provided as a string. ([#34968](https://togithub.com/hashicorp/terraform/pull/34968), [#35224](https://togithub.com/hashicorp/terraform/pull/35224), [#35285](https://togithub.com/hashicorp/terraform/pull/35285)) - core: Performance improvement during graph building for configurations with an extremely large number of `resource` blocks. ([#35088](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/pull/35163)) - `terraform output` with `cloud` block: Terraform no longer suggests that data loss could occur when outputs are not available. ([#35143](https://togithub.com/hashicorp/terraform/issues/35143)) - `terraform console`: Now has basic support for multi-line input in interactive mode. ([#34822](https://togithub.com/hashicorp/terraform/pull/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](https://togithub.com/hashicorp/terraform/issues/35164)) - `removed` blocks can now declare destroy-time provisioners which will be executed when the associated resource instances are destroyed. ([#35230](https://togithub.com/hashicorp/terraform/issues/35230)) BUG FIXES: - `remote-exec` provisioner: Each remote connection will now be closed immediately after use. ([#34137](https://togithub.com/hashicorp/terraform/issues/34137)) - backend/s3: Fixed the digest value displayed for DynamoDB/S3 state checksum mismatches. ([#34387](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/35180)) - config: `import` blocks which referenced resources in non-existent modules were silently ignored when they should have raised an error ([#35330](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/35181)) - `import`: `import` blocks could block a destroy operation if the target resource was already deleted ([#35272](https://togithub.com/hashicorp/terraform/issues/35272)) - `cli`: plan output was missing blocks which were entirely unknown ([#35271](https://togithub.com/hashicorp/terraform/issues/35271)) - `cli`: fix crash when running `providers mirror` with an incomplete lock file ([#35322](https://togithub.com/hashicorp/terraform/issues/35322)) - core: Changing `create_before_destroy` when replacing an instance, then applying with `-refresh=false` would order the apply operations incorrectly ([#35261](https://togithub.com/hashicorp/terraform/issues/35261)) - core: Resource addresses that start with the optional `resource.` prefix will now be correctly parsed when used as an address target. ([#35333](https://togithub.com/hashicorp/terraform/issues/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: - [v1.8](https://togithub.com/hashicorp/terraform/blob/v1.8/CHANGELOG.md) - [v1.7](https://togithub.com/hashicorp/terraform/blob/v1.7/CHANGELOG.md) - [v1.6](https://togithub.com/hashicorp/terraform/blob/v1.6/CHANGELOG.md) - [v1.5](https://togithub.com/hashicorp/terraform/blob/v1.5/CHANGELOG.md) - [v1.4](https://togithub.com/hashicorp/terraform/blob/v1.4/CHANGELOG.md) - [v1.3](https://togithub.com/hashicorp/terraform/blob/v1.3/CHANGELOG.md) - [v1.2](https://togithub.com/hashicorp/terraform/blob/v1.2/CHANGELOG.md) - [v1.1](https://togithub.com/hashicorp/terraform/blob/v1.1/CHANGELOG.md) - [v1.0](https://togithub.com/hashicorp/terraform/blob/v1.0/CHANGELOG.md) - [v0.15](https://togithub.com/hashicorp/terraform/blob/v0.15/CHANGELOG.md) - [v0.14](https://togithub.com/hashicorp/terraform/blob/v0.14/CHANGELOG.md) - [v0.13](https://togithub.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md) - [v0.12](https://togithub.com/hashicorp/terraform/blob/v0.12/CHANGELOG.md) - [v0.11 and earlier](https://togithub.com/hashicorp/terraform/blob/v0.11/CHANGELOG.md)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 these updates again.
This PR has been generated by Renovate Bot.