neurogenesis

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

neurogenesis

Start with terraforming:

• http://terraforming.dtan4.net
• https://github.com/dtan4/terraforming

This has become my defacto choice for generating terraform resources from existing infrastructure.

A little more details on what this workflow might look like, assuming you're on Amazon (applies to others). It's more or less an iterative TDD process for terraform. I've even used "guard" with "terraform apply" on file changes to speed things up a bit.

Break your infrastructure into app services vs core / shared components. Shared components might be network scaffolding like VPCs and all of the related networking that (a) rarely ever changes and (b) is incredibly risky if it does (i.e. replacing a subnet might cause servers to be re-created).

neurogenesis

#!/usr/bin/env ruby

# USAGE:
#   gem install terraforming
#   export AWS_PROFILE=xxx
#   mkdir -p ~/projects/terraform
#   cd ~/projects/terraform
#   mkdir -p imports/[account]/[region]
#   cd imports/[account]/[region]
#   ../../../bin/terraforming-import-all

neurogenesis

#!/usr/bin/env bash
#
# TODO:
#   - allow setting custom green/yellow threshold via CLI options
#   - allow profile selection via CLI options
#   - fix issue with command argument position (must follow hostname)
#

## set defauts