Internet down, infrastructure as code up: Terraform 1.0 finally lands

Internet down, infrastructure as code up: Terraform 1.0 finally lands

While the rest of the internet ground to a halt due to a hiccup at CDN Fastly, HashiConf Europe went ahead on YouTube to give users what they have been asking for: Terraform 1.0.

Though senior software engineer Kristin Laemmert already assured users that the infrastructure as code tool would be good to use in production last year, the final move to 1.0 is meant to make its proficiency for working at scale official. According to HashiCorp CTO Mitchell Hashimoto, v1.0 mainly offers enterprises a bit of security, since it means that the days of breaking updates are over and there’s greater interoperability when it comes to Terraform states.

And indeed, ops folks gasping for new features will have to wait till the first minor release of the 1.x series, since the Terraform team used the last couple of months to get the tool into a stable form. This included refactoring internals (secret handling for example), fixing bugs, removing deprecated provisioners and backends, and committing to plugin protocol support. 

With Terraform in a stable state, the company now promises an extended maintenance period of at least 18 months. Fixes, however, may be released in upcoming 1.x releases and not necessarily 1.0.x ones.

Looking towards the Terraform future, testing is something the community has been asking for for years, so this is something the company looks to tackle in the 1.x series. Laemmert, who was around again to discuss the new release, also mentioned her team looking into an “everything is a plan” approach, configuration-based state operations, and Terraform cloud integration enhancements. Other areas of improvement will include the CDK, but other than that HashiCorp is intent on listening to the community to come up with a roadmap. 

Looking at software as a service offering Terraform Cloud, HashiCorp co-founder Armon Dadgar introduced users to a native workflow to publish modules directly from a public registry into an organisation’s private registry. 

A new Workspace Overview is meant to give users an easier way to visualise “workspaces, resources managed, outputs, and details of runs”. Questions about plans to have a private provider registry were answered by Sr Technical Product Marketing Manager Kyle Ruddy with a rather nebulous “fingers crossed it might be a thing.”

Terraform Run Checks for third-party integrations haven’t quite made it in time for HashiConf, but the company apparently plans to open a public beta “during summer”.