Terragrunt v0.0.1, with DynamoDB locking

.gitignore

@@ -1,2 +1,3 @@
 .idea
 vendor
+.terragrunt

README.md

@@ -0,0 +1,205 @@
+# Terragrunt
+
+Terragrunt is a thin wrapper for the [Terraform client](https://www.terraform.io/) that provides a distributed locking
+mechanism which allows multiple people to collaborate on the same Terraform state without overwriting each other's
+changes. Terragrunt currently uses Amazon's [DynamoDB](https://aws.amazon.com/dynamodb/) to acquire and release locks.
+DynamoDB is part of the [AWS free tier](https://aws.amazon.com/dynamodb/pricing/), so if you're already using AWS, this
+locking mechanism should be completely free. Other locking mechanisms may be added in the future.
+
+## Motivation
+
+When you use Terraform to provision infrastructure, it records the state of your infrastructure in [state 
+files](https://www.terraform.io/docs/state/). In order to make changes to your infrastructure, everyone on your
+team needs access to these state files. You could check the files into version control (not a great idea, as the state
+files may contain secrets) or use a supported [remote state 
+backend](https://www.terraform.io/docs/state/remote/index.html) to store the state files in a shared location such as 
+[S3](https://www.terraform.io/docs/state/remote/s3.html), 
+[Consul](https://www.terraform.io/docs/state/remote/consul.html), 
+or [etcd](https://www.terraform.io/docs/state/remote/etcd.html). The problem is that none of these options provide 
+*locking*, so if two team members run `terraform apply` on the same state files at the same time, they may overwrite 
+each other's changes. The official solution to this problem is to use [Hashicorp's 
+Atlas](https://www.hashicorp.com/atlas.html), but that requires using a SaaS platform for all Terraform operations and
+can cost a lot of money.
+
+The goal of Terragrunt is to provide a simple, free locking mechanism that allows multiple people to safely collaborate
+on Terraform state.
+
+## Install
+
+1. Install [Terraform](https://www.terraform.io/).
+1. Install Terragrunt by going to the [Releases Page](https://github.com/gruntwork-io/terragrunt/releases), downloading
+   the binary for your OS, renaming it to `terragrunt`, and adding it to your PATH.
+
+## Quick start
+
+Go into the folder with your Terraform templates and create a `.terragrunt` file. This file uses the same
+[HCL](https://github.com/hashicorp/hcl) syntax as Terraform and is used to configure Terragrunt and tell it how to do
+locking. To use DynamoDB for locking (see [Locking using DynamoDB](#locking-using-dynamodb)), `.terragrunt` should
+have the following contents:
+
+```hcl
+lockType = "dynamodb"
+stateFileId = "my-app"
+```
+
+Now everyone on your team can use Terragrunt to run all the standard Terraform commands:
+
+```bash
+terragrunt get
+terragrunt plan
+terragrunt apply
+terragrunt output
+terragrunt destroy
+```
+
+Terragrunt forwards most commands directly to Terraform. However, for the `apply` and `destroy` commands, it will first 
+acquire a locking using [DynamoDB](#locking-using-dynamodb):
+
+```
+terragrunt apply
+[terragrunt] 2016/05/30 16:55:29 Attempting to acquire lock for state file my-app in DynamoDB
+[terragrunt] 2016/05/30 16:55:30 Attempting to create lock item for state file my-app in DynamoDB table terragrunt_locks
+[terragrunt] 2016/05/30 16:55:30 Lock acquired!
+[terragrunt] 2016/05/30 16:55:30 Running command: terraform apply
+terraform apply
+
+aws_instance.example: Creating...
+  ami:                      "" => "ami-0d729a60"
+  instance_type:            "" => "t2.micro"
+
+[...]
+
+Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
+
+[terragrunt] 2016/05/27 00:39:19 Attempting to release lock for state file my-app in DynamoDB
+[terragrunt] 2016/05/27 00:39:19 Lock released!
+```
+
+## Locking using DynamoDB
+
+Terragrunt can use Amazon's [DynamoDB](https://aws.amazon.com/dynamodb/) to acquire and release locks. DynamoDB supports
+[strongly consistent reads](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.DataConsistency.html)
+as well as [conditional writes](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.SpecifyingConditions.html),
+which are all the primitives we need for a very basic distributed lock system. It's also part of [AWS's free
+tier](https://aws.amazon.com/dynamodb/pricing/), and given the tiny amount of data we are working with and the 
+relatively small number of times per day you're likely to run Terraform, it _should_ be a free option for teams already
+using AWS. We take no responsibility for any charges you may incur.
+
+#### DynamoDB locking prerequisites
+
+To use DynamoDB for locking, you must:
+
+1. Already have an AWS account.
+1. Set your AWS credentials in the environment using one of the following options:
+    1. Set your credentials as the environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+    1. Run `aws configure` and fill in the details it asks for.
+    1. Run Terragrunt on an EC2 instance with an IAM Role.
+1. Your AWS user must have an [IAM 
+   policy](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/access-control-identity-based.html) 
+   granting all DynamoDB actions (`dynamodb:*`) on the table `terragrunt_locks` (see the
+   [DynamoDB locking configuration](#dynamodb-locking-configuration) for how to configure this table name). Here is an 
+   example IAM policy that grants the necessary permissions on the `terragrunt_locks` table in region `us-west-2` for
+   an account with account id `1234567890`:
+
+    ```json
+    {
+      "Version": "2012-10-17",
+      "Statement": [{
+        "Sid": "",
+        "Effect": "Allow",
+        "Action": "dynamodb:*",
+        "Resource": "arn:aws:dynamodb:us-west-2:1234567890:table/terragrunt_locks"
+      }]
+    }
+    ```
+
+#### DynamoDB locking configuration
+
+For DynamoDB locking, Terragrunt supports the following settings in `.terragrunt`:
+
+```hcl
+lockType = "dynamodb"
+stateFileId = "my-app"
+
+dynamoLock = {
+  awsRegion = "us-east-1"
+  tableName = "terragrunt_locks"
+  maxLockRetries = 360
+}
+```
+
+* `lockType`: (Required) Must be set to `dynamodb`.
+* `stateFileId`: (Required) A unique id for the state file for these Terraform templates. Many teams have more than
+  one set of templates, and therefore more than one state file, so this setting is used to disambiguate locks for one 
+  state file from another.
+* `awsRegion`: (Optional) The AWS region to use. Default: `us-east-1`.
+* `tableName`: (Optional) The name of the table in DynamoDB to use to store lock information. Default:
+  `terragrunt_locks`.
+* `maxLockRetries`: (Optional) The maximum number of times to retry acquiring a lock. Terragrunt waits 10 seconds
+  between retries. Default: 360 retries (one hour).
+
+#### How DynamoDB locking works
+
+When you run `terragrunt apply` or `terragrunt destroy`, Terragrunt does the following:
+
+1. Create the `terragrunt_locks` table if it doesn't already exist.
+1. Try to write an item to the `terragrunt_locks` with `stateFileId` equal to the id specified in your
+   `.terragrunt` file. This item will include useful metadata about the lock, such as who created it (e.g. your 
+   username) and when. 
+1. Note that the write is a conditional write that will fail if an item with the same `stateFileId` already exists.
+    1. If the write succeeds, it means we have a lock!
+    1. If the write does not succeed, it means someone else has a lock. Keep retrying every 10 seconds until we get a
+       lock.
+1. Run `terraform apply` or `terraform destroy`.
+1. When Terraform is done, delete the item from the `terragrunt_locks` table to release the lock.
+
+## Cleaning up old locks
+
+If Terragrunt is shut down before it releases a lock (e.g. via `CTRL+C` or a crash), the lock might not be deleted, and
+will prevent future changes to your state files. To clean up old locks, you can use the `release-lock` command:
+
+```
+terragrunt release-lock
+Are you sure you want to forcibly remove the lock for stateFileId "my-app"? (y/n):
+```
+
+## Developing terragrunt
+
+#### Running tests
+
+**Note**: The tests in the `dynamodb` folder for Terragrunt run against a real AWS account and will add and remove
+real data from DynamoDB. DO NOT hit `CTRL+C` while the tests are running, as this will prevent them from cleaning up
+temporary tables and data in DynamoDB. We are not responsible for any charges you may incur.
+
+Before running the tests, you must configure your AWS credentials as explained in the [DynamoDB locking
+prerequisites](#dynamodb-locking-prerequisites) section.
+
+To run all the tests:
+
+```bash
+go test -v -parallel 128 $(glide novendor)
+```
+
+To run a single test called `TestFoo`:
+
+```bash
+go test -v -parallel 128 -run TestFoo
+```
+
+#### Releasing new versions
+
+To release a new version, just go to the [Releases Page](https://github.com/gruntwork-io/terragrunt/releases) and
+create a new release. The CircleCI job for this repo has been configured to:
+
+1. Automatically detect new tags.
+1. Build binaries for every OS using that tag as a version number.
+1. Upload the binaries to the release in GitHub.
+
+See `circle.yml` and `_ci/build-and-push-release-asset.sh` for details.
+
+## TODO
+
+* Implement best-practices in Terragrunt, such as checking if all changes are committed, calling `terraform get`,
+  calling `terraform configure`, etc.
+* Consider implementing alternative locking mechanisms, such as using Git instead of DynamoDB.
+* Consider embedding the Terraform Go code within Terragrunt instead of calling out to it.