v1.16.0-alpha20260626
📦 terraformView on GitHub →
✨ 7 features🐛 7 fixes🔧 12 symbols
Summary
This alpha release introduces significant new features like support for nested computed values, import blocks in modules, and new resource action failure modes. It also includes several bug fixes related to import blocks, state operations, and provider initialization logging.
Migration Steps
- Verify that configured `bastion_host_key` is correct, as it is now applied correctly.
- If using experimental features, note that `terraform test cleanup` command is available to clean up state files left by failed test operations when using deferred actions or `skip_cleanup`.
✨ New Features
- Providers can now store PlannedPrivate data.
- Introduced a new `store` block in `terraform_data` to handle ephemeral and sensitive values.
- Providers can now use nested blocks as computed values.
- Added support for `import` blocks inside modules.
- Producing builds for Linux s390x (zLinux).
- The `workspace list` command now supports `-json` flag for machine-readable output.
- Resource action triggers can now use `on_failure` modes of `halt`, `taint`, or `continue`.
🐛 Bug Fixes
- Import blocks no longer ignore provider local names.
- Fixed a `terraform apply` panic when the plan contained a no-op change for a deposed object on a resource with `lifecycle.precondition` or `lifecycle.postcondition` defined.
- Terraform now errors if an invalid workspace name becomes selected due to out-of-band actions.
- Terraform now raises a warning when a file referenced via `-filter` flag does not exist.
- Stopped removing locks from the dependency lock file corresponding to providers configured as a `dev_override` during `init`.
- Added warnings during `init` when unmanaged providers are in use and will impact provider installation processes.
- Actions are now invoked with respect to all resource dependencies.