Terragrunt lock region selection ignores AWS_REGION environment variable about terragrunt

[kwilczynski]

@davidski hi there! Sorry for not being clear enough, my bad. Although, you have answered my question, thank you!

[brikis98]

Thanks for filing! Any interest in submitting a PR? It should be a pretty straightforward change.

[davidski]

I currently don't work with Go at all. ☹️ While it's on my To Do list, I'm hoping someone else picks this up before then.

[brikis98]

No worries! We'll see if we can get to this in the next week or two.

[kwilczynski]

This is a simple addition, but here is one question (more about the desired behaviour): given the AWS_REGION environment variable present, should it also override any other place where a region is concerned? For example...

The lock backend (e.g. DynamoDB) can take the desired region from the configuration, but when it goes to the remote state handling, then it works by a virtue of passing arguments to Terraform from the config section of the backend section in the configuration file (these are passed as-is as formatted key-value items). Should the aws_region be overridden here too?

[davidski]

Hey there, @kwilczynski. If I'm following this correctly, if the user enters a remote_state:bucket:region setting, that value (and not the environment value) should be used just as it is today. Manually coded values in a conf file should always override default environment variables.

[brikis98]

Since Terraform now natively supports locking, Terragrunt no longer has locking built in, so I think this issue can be closed.