News for hackers. Stuff that matters.

A comment on Using Actual Code for IaC. Parent comment

Re:Using Actual Code for IaC by octopoc on Friday April 29, 2022 @05:09PM (#31210604)
> every time I've watched the infrastructure description go from something that could easily be tested and reasoned about to an awful mess nobody wants to touch for fear of breakage

We programmers have been dealing with this kind of complexity for a long time, why not use some of the tools normally used to manage complexity in code? For example:

1. Comments

2. Code reviews

3. Gated merge requests

etc. etc.

[ Parent | on HN ]
Re:Using Actual Code for IaC by naserbvqtery on Friday April 29, 2022 @05:24PM (#31210743)
Those things should all still be used with a dsl iac. They're not bringing anything new to the table in the argument of dsl vs general programming language for infrastructure.

Arguably this comment even demonstrates a bit of what I consider one of the biggest problems in the space. It's common for someone who hasn't bought in to dsl based iac tooling to imply dsl based tooling is from a less sophisticated place where modern engineering practices aren't applied, and it's better to grow up and use big-boy tools.

It's almost like they've forgotten the dsl based tooling was in fact built by other application developers with intense subject matter expertise in the space.

[ Parent | on HN ]