Hi folks! Are you going to the GitHub Universe on Nov 13-14 in SF? Or in town that week? Join us at our after-party the evening on the 13th for some 🍺 and fun tech conversations! And if you can't make it to the party but still want to meet us in person? Book a time here 👈
Ben Kehoe, AWS Serverless Hero, presented this at the ServerlessConf NY. He argues that representing our infrastructure using declarative languages is fundamentally better, and that despite the many and varied flaws of YAML, using it and cloud infrastructure management services (like CloudFormation) directly has the lowest TCO.
"For me, the worst issue is the exclusion of comments. Of all the problems we’re leaving to future generations, the complete lack of explanation in the configuration files of future legacy software systems must be among the most irksome. Understanding is good, clear explanations are good; discouraging the use of helpful and clarifying comments is inexcusable." Malcolm Sparks has a short rant about JSON.
Good overview article. I like diagrams.
"The CloudFormation solution to custom logic is lambda. You can use lambdas to create a macro or a custom resource. This approach presents extra complications that don’t exist in Terraform’s approach of semantically versioned git modules." Jack Lindamood shares his experience codifying his infrastructure using Terraform and CloudFormation.
People like to debate it but seems obvious to me - tooling helps. Just as you can impose a workflow through a tool, you can also instill habits through its use.
This tool gives you a real-time stream of leaked secrets 😅 Paul Price is the creator, he is making a point, and he writes about it here.
Join 5,000+ subscribers of hand-curated
Git and DevOps articles