From 599f9239f18bcceecad25b933a5bab51d76f962e Mon Sep 17 00:00:00 2001 From: hc-github-team-tf-core <82990137+hc-github-team-tf-core@users.noreply.github.com> Date: Thu, 18 Sep 2025 13:13:31 +0200 Subject: [PATCH] Prepare before 1.14.0-beta1 release (#37635) --- CHANGELOG.md | 18 +++++++----------- version/VERSION | 2 +- 2 files changed, 8 insertions(+), 12 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 002c7e0fc3..8f2439c6ef 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,10 +1,16 @@ -## 1.14.0 (Unreleased) +## 1.14.0-beta1 (September 18, 2025) NEW FEATURES: +* **List Resources**: List resources can be defined in `*.tfquery.hcl` files and allow querying and filterting existing infrastructure. + +* A new Terraform command `terraform query`: Executes list operations against existing infrastructure and displays the results. The command can optionally generate configuration for importing results into Terraform. + * A new GenerateResourceConfiguration RPC allows providers to create more precise configuration values during import. ([#37515](https://github.com/hashicorp/terraform/issues/37515)) +* New top-level Actions block: Actions are provider defined and meant to codify use cases outside the normal CRUD model in your Terraform configuration. Providers can define Actions like `aws_lambda_invoke` or `aws_cloudfront_create_invalidation` that do something imparative outside of Terraforms normal CRUD model. You can configure such a side-effect with an action block and have actions triggered through the lifecycle of a resource or through passing the `-invoke` CLI flag. ([#37553](https://github.com/hashicorp/terraform/issues/37553)) + ENHANCEMENTS: @@ -27,16 +33,6 @@ UPGRADE NOTES: * Building Terraform 1.14 requires macOS Monterey or later (due to being built on Go 1.25 which imposes these requirements) ([#37436](https://github.com/hashicorp/terraform/issues/37436)) -EXPERIMENTS: - -Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases. - -- The experimental "deferred actions" feature, enabled by passing the `-allow-deferral` option to `terraform plan`, permits `count` and `for_each` arguments in `module`, `resource`, and `data` blocks to have unknown values and allows providers to react more flexibly to unknown values. -- `terraform test cleanup`: The experimental `test cleanup` command. In experimental builds of Terraform, a manifest file and state files for each failed cleanup operation during test operations are saved within the `.terraform` local directory. The `test cleanup` command will attempt to clean up the local state files left behind automatically, without requiring manual intervention. -- `terraform test`: `backend` blocks and `skip_cleanup` attributes: - - Test authors can now specify `backend` blocks within `run` blocks in Terraform Test files. Run blocks with `backend` blocks will load state from the specified backend instead of starting from empty state on every execution. This allows test authors to keep long-running test infrastructure alive between test operations, saving time during regular test operations. - - Test authors can now specify `skip_cleanup` attributes within test files and within run blocks. The `skip_cleanup` attribute tells `terraform test` not to clean up state files produced by run blocks with this attribute set to true. The state files for affected run blocks will be written to disk within the `.terraform` directory, where they can then be cleaned up manually using the also experimental `terraform test cleanup` command. - ## Previous Releases For information on prior major and minor releases, refer to their changelogs: diff --git a/version/VERSION b/version/VERSION index 2f2e08cfa3..9c7ce49735 100644 --- a/version/VERSION +++ b/version/VERSION @@ -1 +1 @@ -1.14.0-dev +1.14.0-beta1