v1.16.0-alpha20260617
📦 terraformView on GitHub →
✨ 7 features🐛 7 fixes🔧 9 symbols
Summary
This alpha release introduces significant new features like support for PlannedPrivate data, the new `store` block in `terraform_data`, and import blocks within modules. It also includes several bug fixes related to import blocks, provider initialization, and resource actions.
Migration Steps
- Users of `provisioner bastion_host_key` should verify that the configured key is now correctly applied and matches expectations.
✨ New Features
- Providers can now store PlannedPrivate data.
- Introduction of a new `store` block within `terraform_data` to handle ephemeral and sensitive values.
- Providers can now utilize nested blocks as computed values.
- Added support for `import` blocks inside modules.
- Terraform now produces builds for the Linux s390x (zLinux) architecture.
- The `workspace list` command now supports a `-json` flag for machine-readable output.
- Resource action triggers can now specify `on_failure` modes: `halt`, `taint`, or `continue`.
🐛 Bug Fixes
- Import blocks no longer ignore provider local names.
- Fixed a `terraform apply` panic occurring when the plan involved a no-op change for a deposed object on a resource configured with `lifecycle.precondition` or `lifecycle.postcondition`.
- Terraform now errors if an invalid workspace name is selected due to out-of-band operations.
- Terraform raises a warning when a file referenced via the `-filter` flag does not exist.
- Fixed an issue where `init` was removing locks from the dependency lock file corresponding to providers configured as `dev_override`.
- Added warnings during `init` when unmanaged providers are in use and might impact provider installation.
- Actions are now invoked respecting all resource dependencies.