v1.16.0-alpha20260715
📦 terraformView on GitHub →
✨ 7 features🐛 9 fixes⚡ 1 deprecations🔧 4 symbols
Summary
This release introduces several new features including enhanced data storage for providers, support for import blocks within modules, and improved machine-readable output for commands like `workspace list`. It also includes numerous bug fixes and enhancements to existing functionalities.
Migration Steps
- Existing usage of bastion_host_key should verify the configured key is correct.
✨ New Features
- Store PlannedPrivate data for providers.
- New store block in terraform_data that can handle ephemeral and sensitive values.
- Providers can now use nested blocks as computed values.
- Add support for import blocks inside modules.
- Produce builds for Linux s390x (zLinux).
- The `workspace list` command can now produce machine-readable output when supplied with the `-json` flag.
- Resource action triggers can now use `on_failure` modes of `halt`, `taint`, or `continue`.
🐛 Bug Fixes
- Import blocks no longer ignore provider local names.
- Fix a `terraform apply` panic when the plan contained a no-op change for a deposed object on a resource whose configuration declared a `lifecycle.precondition` or `lifecycle.postcondition`.
- Terraform will now error if an invalid workspace name becomes selected due to actions performed out-of-band.
- Terraform will now raise a warning when a file referenced via `-filter` flag does not exist.
- Stop removing locks from the dependency lock file corresponding to providers configured as a dev_override.
- Add warnings when unmanaged providers are in use and will impact provider installation processes.
- Actions are now invoked with respect to all resource dependencies.
- Return correct error when import target exists in state, but not config.
- Merge no longer panics with null objects.
Affected Symbols
⚡ Deprecations
- Child module outputs with unreferenced deprecated nested attributes no longer return deprecation warnings.