`script` is bad, but `code` is fine. In this case, it is really a DSL language for cloud configurations.

My circle also just use "code" as far as I'm aware, though I tend to think of it as a definition instead. Template would also fit but you can use templates within Terraform so that could be confusing.

The official name for .tf files is a “configuration”, per the code base.

Which makes sense in the context of managing "configuration as code".

Once configuration is code, i.e. Turing complete, something has gone awry.

Indeed - infrastructure being defined with a declarative model makes perfect sense. One need not use a DSL to achieve that though.

Comprehension, like list comprehension, might be a better term

model