#terragrunt - November 2018

@Gonzalo Peci has joined the channel

@stephen has joined the channel

@Vi has joined the channel

Hi,
I was working with terragrunt and observed that terragrunt does not pick up the changes automatically for modules. Is there any way to sort this out?

pass --terragrunt-source-update

@Vi ^^^

terragrunt uses a hash of the source url to determine whether the source has changed. if you are using tagged/versioned modules, that works great... you update the source ref, and terragrunt will detect the changed hash and automatically pull down the new version

if you are not using a version ref in your source, then you can use --terragrunt-source-update to force terragrunt to pull down the source

has anyone played around with the terraform 0.12 rc with terragrunt?

What is the usecase for terragrunt with workspaces module etc?

@Erik Osterman (Cloud Posse) not yet, but should do it after AWS re:invent.

@Anmol has joined the channel

Hi guys! If you want to check how I do dynamic parameters in static terraform.tfvars with Terragrunt and tell me if you know better solution, you should read my blog post (and try it) - https://medium.com/@anton.babenko/modules-tf-convert-visual-aws-diagram-into-terraform-configurations-e61fb0574b10

@Bogdan has joined the channel

Hello everyone,
I am trying to run terragrunt plan using circleci and I am getting the following error

 [terragrunt] [/root/project/cloudfront_frontend] 2018/11/26 03:21:58 The non-interactive flag is set to true, so assuming 'yes' for all prompts
[terragrunt] [/root/project/cloudfront_frontend] 2018/11/26 03:21:58 Creating S3 bucket cb-terraform-infra-state-sit
[terragrunt] 2018/11/26 03:21:59 AccessDenied: Access Denied
	status code: 403, request id: 35E32BD7CF45BED5, host id: f3c85r+xX5QKBmRdlhW8JCQyj+AqUtKGZWwLvbuo/YkjErGKUuVJ6kAs0NIjooDC83uXs1JkjXc=
[terragrunt] 2018/11/26 03:21:59 Unable to determine underlying exit code, so Terragrunt will exit with error code 1
Exited with code 1

I have the credentials in place ~/.aws/credentials . It works perfectly in local. Not sure how to fix it 😞

I am using the following docker image antonbabenko/terracing:v0.0.6

It looks like permission issue but I have given fullAdminAccess to the user.

hrm… so shouldn’t need to write credentials to ~/.aws/credentials

using the standard AWS envs should be sufficient

AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

in fact, i’d try to get it working with ENVs locally (for testing)

then once you find the working combination, that’s what you’ll set in circle

@joshmyers has joined the channel

@jerry has joined the channel

set the channel topic: