Hacker News new | past | comments | ask | show | jobs | submit login

What's wrong with having your infrastructure as code and storing it in Git?



Nothing. Even if it's objectively terrible (thousands of lines of templated YAML, or thousands of lines of spaghetti bash), being in Git as code is still better. At least you know what it is, how it evolved, and can start adding linting/tests.


I manage large IaC repos and it's mostly HCL, well-structured and easy to work with. Where we have Kubernetes manifests, they're usually split into smaller files and don't cause any trouble as normally we usually don't deploy manifests directly.


YAML isn't code. Same as your reply, YAML has very little awareness of context.


In computer science, the word "code" has a very specific meaning, and markup languages definitely fit this definition.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: