News for hackers. Stuff that matters.
Re:Infrastructure as Code, Part One by pm90 on Saturday April 13, 2019 @06:38PM (#19656195)
... until your jinja templating breaks for some obscure reason, or the underlying terraform resource upgrades (they follow the provider api after all), or if you need to do some state surgery and partition one terraform state into multiple ones, or until you want to import resources into the generated terraform or....

Apologies, I don't mean to be a downer. But... you're making your present life easier but making the code harder to maintain for future maintainers of your codebase.

Re:Infrastructure as Code, Part One by detaro on Saturday April 13, 2019 @08:39PM (#19656755)
What's the more maintainable alternative? Is writing repeated constructs etc out individually really more maintainable, or are you referring to other ways of getting these things reduced?
Re:Infrastructure as Code, Part One by nitelord on Saturday April 13, 2019 @09:53PM (#19657054)
I highly recommend taking a look at the AWS CDK. It's a relatively new project, still in beta and hasn't gotten a lot of attention yet. It allows you to use real programming languages to generate Cloudformation templates. In my eyes this is the best of both worlds.
Re:Infrastructure as Code, Part One by pm90 on Saturday April 13, 2019 @09:39PM (#19656996)
Just plain terraform modules, for now.

I’m eagerly awaiting 0.12 so the language would have similar features as jinja templating.