You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
josiah 4d045744ff
Deploy chat to mattermost in
2 months ago
bikeshed Manage VMs in TF better; remove testchat. 2 months ago
do_domains Deploy chat to mattermost in 2 months ago Move to using DO:Spaces as state backend. 12 months ago Remember what public key you want. 7 months ago


The TF module of ADC handles a few things:

  • inits machine creation in Bikeshed, my local proxmox cluster
  • configures DNS for my projects.

The idea is to keep ansible for configuration and use TF for machine creation / API communication.

Using this

  • Install Terraform
  • Move into the directory related to what you want to work on
  • terraform plan
  • terraform apply

State management

Using local tf state is mostly reasonable for a personal project, but I wanted to learn TF for enterprise reasons too, so I'm using Digital Ocean Spaces as an s3 compatible storage system. This is an explicit risk!! Sensitive shit can get written to those locations and leak keys or sensitive data to others.

See the Exceptions area under secrets for mroe info.


If and when you need to import stuff from outside of Terraform, use terraformer:

This is how I got everything in here in the first place!


secrets are managed via pass, mostly

Add secrets

  1. install pass
  2. pass init `your gpg id` - make sure you use the right one, jesus FUCK. you want this public key: `98D96C71214AFB7583C03F5EDC798A32AE57BA46`

pass insert <your secret name>

Reference secrets

export TF_VAR_DO_PAT=$(pass <your secret name>)

Exceptions (digital ocean spaces access for backend storage):

  1. Install the awscli tool.
  2. aws configure --profile digitalocean
  3. Fill in the fields with your key id and secret
  4. export AWS_PROFILE=digitalocean
  5. Boom.