2020-02-03, 14:50–15:15, B.1.015
One of the most frequent complaints about Terraform is the state that configuration gets itself into after a repository have been living for a few years. The root cause is often that teams treat Terraform as configuration instead of code, and throw basic software engineering principles out the window as a result. In this talk, we'll look at proven patterns for writing Terraform configuration which ages well and remains an asset instead of a liability.
James is a software engineer from Bath, England. He is currently the chief architect at database company Event Store and a contributor to Pulumi. He was formerly a core maintainer of Terraform at HashiCorp, worked on cloud infrastructure at Joyent and was the first VP Engineering at Jet.com.