Terraform Gotchas and How We Work Around Them

Re:Terraform Gotchas and How We Work Around Them by mental_ on Monday June 12, 2017 @06:19PM (#14541589)

I thought terragrunt was a must have for that kind of deployment.

[ Parent | on HN ]

Re:Terraform Gotchas and How We Work Around Them by brazzledazzle on Monday June 12, 2017 @06:28PM (#14541624)

I'm curious about that as well. I was told by coworkers that Hashicorp added support for DynamoDB which rendered terragrunt redundant but I haven't had time to look into it.

[ Parent | on HN ]

Re:Terraform Gotchas and How We Work Around Them by Florin_Andrei on Monday June 12, 2017 @07:16PM (#14541896)

terraform {

  backend "s3" {

    region = "us-west-1"

    bucket = "foo-tf-us-west-1"

    key = "foobar.tfstate"

    dynamodb_table = "tf-lock"

  }

}

https://www.terraform.io/docs/backends/types/s3.html#dynamod...

[ Parent | on HN ]

Re:Terraform Gotchas and How We Work Around Them by tjbiddle on Tuesday June 13, 2017 @09:26AM (#14544527)

Awesome! Any idea when this was added? I feel like this wasn't in the documentation a week or two ago; everything had still said "Use Hashicorp Atlas for remote state locking".

[ Parent | on HN ]

Re:Terraform Gotchas and How We Work Around Them by Florin_Andrei on Tuesday June 13, 2017 @01:49PM (#14546878)

I've been using it for weeks if not months.

Their documentation might be lagging occasionally. It's a small team tackling a big challenge.

[ Parent | on HN ]