v1.16.0-alpha20260701
📦 terraformView on GitHub →
✨ 7 features🐛 8 fixes🔧 7 symbols
Summary
This alpha release introduces significant new features like nested computed values for providers and support for import blocks in modules, alongside various bug fixes and enhancements to provider initialization and action triggering.
Migration Steps
- Existing usage of `provisioner bastion_host_key` should be verified to ensure the configured key is correct.
✨ New Features
- Providers can now store PlannedPrivate data.
- Introduction of a new store block in terraform_data to handle ephemeral and sensitive values.
- Providers can now use nested blocks as computed values.
- Support for import blocks inside modules has been added.
- Builds for Linux s390x (zLinux) are now produced.
- The `workspace list` command supports machine-readable output via the `-json` flag.
- Resource action triggers now support `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 involved a no-op change for a deposed object with defined `lifecycle.precondition` or `lifecycle.postcondition`.
- Terraform now errors if an invalid workspace name is selected due to out-of-band actions.
- Terraform raises a warning when a file referenced via the `-filter` flag does not exist.
- Initialization process stops removing locks from the dependency lock file corresponding to providers configured as a dev_override.
- Warnings are added during init when unmanaged providers are in use and might impact provider installation.
- Actions are now invoked respecting all resource dependencies.
- Merge operation no longer panics when encountering null objects.