TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities and articles.
Top engineers at Anthropic and OpenAI say AI now writes 100% of their code.
If you're not using AI, you're spending 40 hours doing what they do in 4.
These 100+ Claude Code hacks fix that and help you ship 10x faster.
Sign up for The Code and get:
100+ Claude Code hacks used by top engineers — free
The Code newsletter — learn the latest AI tools, tips, and skills to code faster with AI in 5 minutes a day
Use Case
GitHub Actions Workflow for Terraform workspaces
Terraform workspaces are essential for managing different environments within the same configuration, such as development, staging, and production. Without them, keeping track of changes and maintaining consistency across environments would be chaotic, if not impossible.
Some of you might already be familiar with this. Let’s quickly go over how workspaces actually work.
How Workspaces Work in Terraform:
Each environment is assigned a unique state file to keep configurations isolated.
Switch between environments by selecting the corresponding state file.
Commands like
terraform workspace newandterraform workspace selectare used to create and switch between environments.The active environment determines which state file Terraform uses during operations.
State files are stored in a backend, and each environment's state is kept separate.
Popularly used backends - S3, GCS, or Blob Storage.
Products like Scalr and Terraform Cloud provide an inbuilt option to maintain the workspaces and respective state files.
This diagram will help simplify how Terraform workspaces integrate with GitHub Actions to manage environments.
GitHub Actions Workflow for Terraform workspaces Architecture
Step 1: Infra team writes Terraform configuration files ( main.tf, providers.tf, etc.) to define infrastructure.
Step 2: Code is pushed to GitHub, triggering an automated workflow using GitHub Actions.
Step 3: GitHub Actions execute Terraform to validate the workspace-specific state files from the backend.
Step 4: Terraform ensures consistency across workspaces and performs provisioning based on the validated state files.
Step 5: Resources are provisioned across cloud environments like AWS, Azure, or Google Cloud based on the validated configurations.
Sample GitHub Actions yaml:
name: Terraform CI/CD
on:
push:
branches:
- main
- 'workspace/*'
jobs:
terraform:
runs-on: ubuntu-latest
steps:
- name: Checkout Code
uses: actions/checkout@v2
- name: Set up Terraform
uses: hashicorp/setup-terraform@v2
with:
terraform_version: <x.y.z>
- name: Terraform Init
id: init
run: terraform init -backend-config=backend.tfvars
- name: Select Terraform Workspace
id: workspace
run: terraform workspace select ${GITHUB_REF##*/} || terraform workspace new ${GITHUB_REF##*/}
- name: Terraform Validate
id: validate
run: terraform validate
- name: Terraform Plan
id: plan
run: terraform plan -out=tfplan -input=false
- name: Terraform Apply
id: apply
if: github.ref == 'refs/heads/main'
run: terraform apply -input=false tfplanExplanation:
on: push: The workflow is triggered on pushes to the
mainbranch and any branch that follows the patternworkspace/*, representing different Terraform workspaces.terraform init: Initializes Terraform and configures the backend using the
backend.tfvarsfile.workspace select/new: Selects the appropriate workspace based on the branch name or creates it if it doesn’t exist.
terraform validate: Validates the Terraform configuration files.
terraform plan: Creates a plan to show what changes Terraform will make.
terraform apply: Applies the plan if the push is to the
mainbranch, ensuring that only validated code in the main branch impacts the actual infrastructure.
This file can be customized further based on your specific requirements and environment configurations.
p.s. if you think someone else you know may like this newsletter, share with them to join here
Tool Of The Day
Standardize confidential computing at the pod level and simplify its consumption in Kubernetes.
Trends & Updates
Resources & Tutorials
Picture Of The Day
Nat Friedman, Satya Nadella, and Chris Wanstrath posing with the Octocat, marking the moment GitHub officially joined Microsoft in a $7.5 billion acquisition.
Was Microsoft's $7.5 billion GitHub acquisition worth it?
Did someone forward this email to you? Sign up here
Interested in reaching smart techies?
Our newsletter puts your products and services in front of the right people - engineering leaders and senior engineers - who make important tech decisions and big purchases.
