Keynote: Terraform 0.13 - Doing More with Modules
Jun 22, 2020
One of the biggest new features of Terraform 0.13 is that "counts", "for_each", and "depends_on" can now be used on modules, not just resources.
- Armon DadgarCo-founder and CTO, HashiCorp
Modules were an abstract entity in Terraform previously. What we found was that users wanted to manipulate them like resources using
depends_on, but they were unable to.
Users were sometimes forced to repeatedly copy and paste modules multiple times. In this keynote session by HashiCorp co-founder Armon Dadgar, you'll learn how Terraform 0.13 made module automation a lot more streamlined, plus you'll see all the other great features Terraform 0.13 has in action.
Today, the biggest enhancement for Terraform users is the new support for module counts, for_each, depends_on, and more. This is going to simplify and reduce the size of many Terraform configurations.
Learn more in the 0.13 beta guide.
Helping users get from an open source on-prem deployment of Terraform to a Terraform Cloud deployment easily was very important in recent releases. Since it's release last month, Terrform Login has simplified the connection of the Terraform CLI to Terraform Cloud. This will help existing OSS users continue with their CLI workflow while making use of remote state and remote runs from Terraform Cloud.
Auto-Installation of Third-Party Providers
In the past, Terraform treated all providers as part of the HashiCorp namespace. community providers were difficult to use and install, and partner providers weren’t differentiated from HashiCorp-supported providers. Terraform could only use the HashiCorp public provider registry.
Terraform 0.13 now has required providers syntax which helps simplify the installation of community providers. This means Terraform can now distinguish between official HashiCorp-supported providers & HashiCorp partner-supported providers.
The Terraform Provider Registry now includes HashiCorp, Partner, and Community providers.