New in Terraform 1.15: Dynamic Sources, Variable Deprecation, and More

New in Terraform 1.15: Dynamic Sources, Variable Deprecation, and More

HashiCorp Blog
HashiCorp BlogMay 13, 2026

Why It Matters

These features tighten IaC governance, reduce runtime errors, and broaden Terraform’s enterprise‑grade usability across cloud and on‑prem environments.

Key Takeaways

  • Dynamic sources accept const variables during init
  • Deprecated attribute surfaces migration warnings early
  • Convert function eliminates ambiguous type inference
  • Windows ARM64 binaries enable Terraform on new hardware
  • S3 backend now supports AWS login credentials

Pulse Analysis

Terraform’s 1.15 release marks a turning point for infrastructure‑as‑code teams seeking tighter control over module composition. By allowing variables flagged as const to be interpolated into module source paths, organizations can parameterize repository locations, branch names, or environment‑specific folders without hard‑coding paths. This capability streamlines CI/CD pipelines, reduces duplication across environments, and aligns Terraform’s behavior with modern GitOps workflows where module versions are often driven by external variables.

Maintainability also receives a boost through the new deprecated attribute for both input variables and output blocks. Instead of silently breaking downstream configurations, Terraform now emits clear diagnostics, giving operators a safety net to phase out legacy interfaces. Coupled with the convert function, which offers explicit inline type casting, the release curtails common pitfalls such as mismatched collection types or ambiguous empty literals. These improvements translate into fewer plan‑time failures and lower the cognitive load on engineers who must juggle complex HCL expressions.

Beyond language refinements, Terraform 1.15 expands its platform and security footprint. Native Windows ARM64 binaries open the door for developers on Surface devices and Mac‑based ARM VMs, while S3 backend support for the new aws login method eliminates long‑lived access keys, aligning Terraform with zero‑trust credential practices. Output type constraints, mock‑function allowances in the test framework, and variable validation blocks for Stacks further cement Terraform’s position as an enterprise‑ready tool that balances flexibility with rigorous validation. Collectively, these enhancements accelerate adoption in regulated industries where auditability and reproducibility are paramount.

New in Terraform 1.15: Dynamic sources, variable deprecation, and more

Comments

Want to join the conversation?

Loading comments...