4 ms·

I've silently been a big fan of this approach for years but hadn't heard about it anywhere (most likely because I'm not familiar with Pulumi). Could you provid

• getmeinrn 3y ago
  This is the closest example I could find https://www.pulumi.com/docs/concepts/how-pulumi-works/ https://www.pulumi.com/docs/concepts/how-pulumi-works/ Pulumi serves as the strongest contender to Terraform when doing IaC (infrastructure as code). Terraform attempts to be a declarative markup language (HCL) but it has a lot of weird imperative quirks due to (understandably) trying to support common complex use cases. In the end they have a clunky custom language that tries to do what general programming languages have done well forever. Pulumi doesn't re-invent the wheel, and lets programming languages do what they do best. Pulumi only really cares that the programming language generates a declarative spec that can be used to compare with your infrastructure. It's the best of both worlds.
  • codethief 3y ago
    Thanks so much! > Pulumi only really cares that the programming language generates a declarative spec that can be used to compare with your infrastructure. It's the best of both worlds. Fully agree! I've called this approach "imperatively generating declarations". Things might get complicated, though, if you try to nest this approach. E.g. if you imperatively generate the structure of your deployment pipeline, which in turn, contains imperative code to generate your infrastructure spec. :) Or something like that[0]. But that's probably just the nature of the problem. [0]: I can't come up with a fully realistic scenario right now because it's late. Maybe tomorrow!