Skip to content
BigConfig
Blog

iac

2 posts with the tag “iac”

Terraform Workspaces Are Not Environments — BigConfig Makes It a Non-Issue

Workspaces are not environments
amiorin
amiorin
Alberto Miorin
Featured

A recurring LinkedIn debate: should you use Terraform workspaces, separate root modules, or copy-pasted folders to isolate environments? Every answer is a tradeoff between WET code, sprawl, and blast radius. This post argues the debate itself is the symptom — Terraform fuses its unit of reuse (the module) with its unit of deployment (the root module + state). BigConfig separates them, treating environments as values passed to packages, and the whole class of problem disappears.

Control planes in BigConfig

rama-jdbc
amiorin
amiorin
Alberto Miorin

A control plane acts as an API for provisioning and managing infrastructure. Well-known examples include AWS itself and Kubernetes (K8s).

A common pain point when using infrastructure-as-code (IaC) tools like Terraform (using HCL) and GitOps is the difficulty in transitioning or upgrading to an internal control plane.

Teams that have invested significant time in writing Terraform’s HCL code traditionally face a complete rewrite to build a custom control plane API over their existing infrastructure definitions.

This limitation is no longer the case with BigConfig. We’ve demonstrated that a functional control plane can be created with as little as 200 lines of code, leveraging existing Terraform configurations.