The Wire · Showcase
TERRAFORM 1.16 ALPHA LANDS WITH EPHEMERAL DATA STORAGE AND NESTED BLOCK SUPPORT
By RepoJournal · Filed · About HashiCorp
Terraform's next major iteration ships with PlannedPrivate data persistence, a new store block for sensitive values, and import block support inside modules that fundamentally expand what providers can express.
Terraform v1.16.0-alpha20260701 [1] dropped overnight with four significant capability additions that close long-standing gaps in provider expressiveness. The new store block in terraform_data [1] gives providers a first-class way to handle ephemeral and sensitive values without treating them as persistent state, solving a coordination problem that's plagued complex deployments. PlannedPrivate data storage [1] lets providers maintain planned values across planning cycles, essential for accurate drift detection. Nested blocks as computed values [1] means providers can return structured data that was previously flattened, and import blocks now work inside modules [1], eliminating a major usability gap. Across the HashiCorp ecosystem, routine dependency bumps landed on terraform-provider-tfcoremock [4], terraform-equivalence-testing [5], and core terraform [2] as actions/setup-go moved from 6.4.0 to 6.5.0, while terraform-schema picked up new CodeDeploy attributes for failure_tolerance and eager_plan [3].
Action items
- → Test Terraform 1.16.0-alpha20260701 in lower environments if you maintain custom providers hashicorp/terraform [plan]
- → Audit provider code for PlannedPrivate and store block adoption opportunities hashicorp/terraform [plan]
- → Update CI pipelines to actions/setup-go 6.5.0 at next sync window hashicorp/terraform [monitor]
References
- [1] v1.16.0-alpha20260701 ↗ hashicorp/terraform
- [2] build(deps): bump actions/setup-go from 6.4.0 to 6.5.0 in the github-actions-backward-compatible group ↗ hashicorp/terraform
- [3] Added: attribute failure_tolerance and eager_plan to deployment_group (#528) hashicorp/terraform-schema
- [4] Bump actions/setup-go from 6.4.0 to 6.5.0 in the github-actions-backward-compatible group ↗ hashicorp/terraform-provider-tfcoremock
- [5] Bump the github-actions-backward-compatible group with 2 updates ↗ hashicorp/terraform-equivalence-testing
FAQ
- What changed in HashiCorp on July 2, 2026?
- Terraform's next major iteration ships with PlannedPrivate data persistence, a new store block for sensitive values, and import block support inside modules that fundamentally expand what providers can express.
- What should HashiCorp teams do about it?
- Test Terraform 1.16.0-alpha20260701 in lower environments if you maintain custom providers • Audit provider code for PlannedPrivate and store block adoption opportunities • Update CI pipelines to actions/setup-go 6.5.0 at next sync window
- Which HashiCorp repositories shipped on July 2, 2026?
- hashicorp/terraform, hashicorp/terraform-schema, hashicorp/terraform-provider-tfcoremock, hashicorp/terraform-equivalence-testing