Skip to content

Latest commit

 

History

History
35 lines (28 loc) · 1.6 KB

README.md

File metadata and controls

35 lines (28 loc) · 1.6 KB

ansible lint ansible lint rules

Infrastructure as Code

There are several goals of this project

  1. a friction-less way to get back to normal after a fresh install of an OS for local devices, and use a common set of expectations for all devices in my fleet
  2. a way to easily provision and deploy cloud resources
  3. a minimal amount of secret management by using 1password

Opinionated Stuff

  • I hate snaps. Wherever possible I use apt on ubuntu.

Terraform

Used to provision cloud resources (currently on digital ocean and aws):

  • compute, dns entries
  • todo: firewall / vpc configs

Read more

Ansible

Used to provision software, services and configuration to all of the machines in my fleet. Read more

Vagrant

Used to run a clean base OS image in a VM (prefer this to docker since its more of a "complete" system). Currently setup to start the VM, and uses a provisioner to deploy ansible roles. The idea with these is to make sure that fresh installs can still provision because over time a system accumulates little changes and can diverge signficantly from a fresh install. Read more

Packer

Not really used right now. If I wanted to make a custom VM image to start from I could do it here, but I've found the vagrant bento images sufficient instead. Read more