Brian Grant

Kelsey talking about configuration as data again. One point he made that I'm increasingly emphasizing: "But when you move to infrastructure as data, we can have these high-level APIs." IaD:IaC is analogous to APIs:scripts. It gives you a surface to manipulate, not just executehttps://twitter.com/GoTimeFM/status/1219683385511161866 …

Do you have a working definition of IaD and IaC? I realized I don't know exactly what people mean by those terms. I think of IaC in terms of dev workflow. You treat it like code, by checking it into a repo with a PR and review. But what gets checked in is static, like YAML.

If someone were checking in a bunch of golang/python/perl scripts that queried a bunch of APIs to dynamically generate config, I wouldn't call that IaC. The "code" I'm thinking of in IaC is declarative and mostly static. So have I actually been thinking of IaD all along?

Anticipating Brian's response: I'm guessing he's using IaD to refer strictly to infrastructure representations using data structures - that might in turn be (easily) manipulated by code. Iow: if you have to "execute" it to find out what it describes then it is IaC and not IaD.