Yoke: Infrastructure as code, but actually

Yoke is really cool Published on 03/02/2025 , 3827 words, 14 minutes to read Infrastructure as code, but actually A group of seals swimming in the ocean near Santa Cruz, California - Photo by Xe Iaso, Canon EOS R6 mk II, Helios 44-2 58mm f/2 One of the biggest memes in site reliability is "infrastructure as code". This is usually very well-intentioned, but there's one small problem: data "aws_route53_zone" "cetacean_club" { name = "cetacean.club." } resource "aws_route53_record" "A" { zone_id = data.aws_route53_zone.cetacean_club.zone_id name = "ingressd. $ { data . aws_route53_zone . cetacean_club . name } " type = "A" ttl = "300" records = [ resource.vultr_instance.my_instance.main_ip ] } This is not code. This is configuration. Sure you manage the configuration with the same tools you use to manage code, you can lint it like it is code, but it's not code. It's a fairly limited DSL that makes it easy to get infrastructure up and running. Let's say you create a new server and yo ... Read full article.