Command Palette

Search for a command to run...

GitHubGitHub

Infrastructure as Code

Install and configure Terraform, Ansible, HashiCorp Vault, Consul, Vagrant and Packer with reproducible infrastructure examples, secret management patterns and safe rollout strategies.

Infrastructure as code turns hand-rolled servers into reviewed, repeatable and versioned changes. These guides cover the tools that make that possible — from provisioning to secret management and golden image building.

Every guide is written against the current release line and verified against the upstream documentation:

GuideCurrent releaseWhat it covers
Terraform1.16.6Providers, remote state, locking, terraform test
Ansible14.5.0 / core 2.21.5Inventory, playbooks, Vault, execution environments
HashiCorp Vault2.2.0Init and unseal, secrets engines, AppRole, audit
HashiCorp Consul2.0.4Cluster, ACLs, TLS, service intentions, Connect
Vagrant2.4.9Boxes, providers, synced folders, multi-machine
HashiCorp Packer1.16.1HCL2 templates, plugins, multi-cloud, attestations

What you will learn

  • Terraform — initialise workspaces, model resources in HCL, plan safely and apply changes.
  • Ansible — write inventories and playbooks, and configure fleets of hosts idempotently.
  • Vault — enable secret engines, issue dynamic credentials and audit access.
  • Consul — provide service discovery and distributed configuration.
  • Vagrant — spin up reproducible development environments from code.
  • Packer — build golden machine images for every target platform.

Safe rollout principles

  1. Commit infrastructure code and review it like application code
  2. Always run plan (or --check) before applying
  3. Keep state in a remote, versioned backend
  4. Store credentials in Vault or your cloud secret manager — never in .tfvars
  5. Roll out incrementally with canaries and blue/green releases