jq1.io

What’s better than 5 semantic outputs?

Previously, the routing policy language gave cloud network engineers a way to express topology intent through four algebraic primitives.

Compiling Cloud Network Topology I think cloud network engineers should take a serious look at the compilation approach given the routing policy language fell out of the architecture naturally.

What began as a modular Terraform experiment evolved into a full compiler-style architecture for AWS networking.

Hey everyone, Great news!

Reflection in the Rear-View: Initially, I thought the TNT Architecture project and Super Router project were “good enough” to scale VPCs and TGWs in AWS.

Aaaand we’re back with another heavy hitting round of super refactorization in Terraform!

What’s up world?!

Welcome to the next episode of thinking out loud to route in the cloud, you know my steez!

Lately, I’ve seen quite a bit of Terraform snippets that use a static map of maps to directly configure resources.

Intro Initially I’d planned to blog more than just about Terraform but it hasn’t turned out that way due to lack of time.

Today’s Mathematics Dynamic VPC x Tiered Subnet Calculator = Tiered VPC Observing Abstractions In hindsight, the Dynamic VPC module should instead be called Simple VPC.

I’ve been thinking about adding support for building tiered subnets of any valid size for the next iteration of the Dynamic VPC Module (which ended up being called Tiered VPC-NG).

I took an internal dev challenge at work a while back because I wanted to learn more Go since I have an OO background and was not familiar with the procedural way of thinking.

At work we’re planning on having our IaC to grow up a bit.

The other day I was wondering if it was possble to unpack a list of elements as args to a function in Terraform similar to * in Python or splat in Ruby?

TL;DR Just show me the code!

“Some callin it fate while some others remain torn, some callin it rain cuz thats when I brainstorm.” - Evidence