Azure Terraformer

There's less than a week until HashiConf! Are you going? I'll see you in Boston ?? https://bit.ly/3AElSMi #hashicorp #hashiconf #boston #cloud #automation

Null is not nothing. It’s a value type in Terraform who’s never invited to the party but always seems to show up. Instead, I would encourage you to start inviting them, to the module party. Null is not nothing, it is a value that represent the absence of a value. Making it the perfect default value for your input variables. When an input variable of your module isn’t set, Terraform will fall back on the provider’s default for that optional attribute, or the upstream API’s default, if one exists. Any default value for an input variable, other than null, is a value you have to maintain.

I never had a reason to CPU profile Terraform until today when I deployed 20,000 random pets, aiming to create some of the most unusual cycles in a graph imaginable. Typically, there is no reason to profile Terraform, as it will point you to results you can't really change anyways. But if you want to profile Terraform for whatever reason, you can do so using pprof: https://lnkd.in/ecMKYaFy Excess of dependencies causes Terraform to spend more CPU cycles on building and walking the dependency graph. Also, marshaling the state happens sometimes more than once, when you apply for instance, as an artifact is passed between plan and apply. But I'll spare you the all the technical details. A takeaway from today is, avoid marking objects with an explicit dependency using?`depends_on`?unless it’s really necessary, especially within module calls or when referencing modules, as this creates unnecessary dependencies. Don't depends_on it, depend on it.