Terragrunt v0.0.1, with DynamoDB locking #2
Conversation
| @@ -0,0 +1,182 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
BTW, I stole this script from the VAAS repo and made a few minor updates to it.
There was a problem hiding this comment.
Awesome! Not a priority right now, but it'd be nice if we published this as an open source go-based tool.
| echo "Installing dependencies using Glide" | ||
| cd "$REPO" | ||
| glide install | ||
|
|
There was a problem hiding this comment.
Nice call splitting this out into a separate script.
|
This looks fantastic. The dynamo code in particular was surprisingly complex and you did a nice job wrapping that in enough functions to make the code readable. Nice testing, and the locking mechanism is pretty easy to follow. Most of my comments centered around docs, conventions, and defaults, but overall this looks great. Once you've responded to comments, feel free to merge. |
|
Question: are there any conflicts between terragrunt and terraform sub-commands? For example, what happens if I run |
|
|
|
I've made all updates in #4. Merging this one. |
Fix xxx-all commands, attempt #2
tests: add regression tests for 1102
This PR contains the initial implementation of terragrunt. v0.0.1 is just a thin wrapper for the Terraform client that provides locking using DynamoDB. It requires minimal setup, it’s in the free tier, and for teams already using AWS, it provides a really easy way to safely collaborate on Terraform state with minimal changes to their Terraform workflow. In fact, the only change is that you run commands using
terragrunt XXXinstead ofterraform XXX.Note that this PR replaces #1 in this repo (which I’ll close shortly). PR #1 also discussed support for locking using Git (or more specifically, a centralized source of truth for Git, such as GitHub). I began that implementation, and this PR contains commits with that code, but it’s quite a bit messier than the DynamoDB solution. I hit my time cap on the Git hacking and decided to remove it from this initial version. Perhaps, if there is demand for it, we can bring it back in the future.