Changes to .terragrunt file aren't picked up after initial terragrunt run. about terragrunt HOT 4 CLOSED

Could this also be fixed by reloading the .terragrunt every time the command is run?

from terragrunt.

@fortytw2 Thanks for the upvote and comment!

Parsing .terragrunt and executing terraform remote config on every run of Terragrunt would solve the problem, but I'd prefer to avoid running terraform remote config on every single Terraform run in case that causes side effects.

For example, Terraform expects the terraform remote config command to be run only once, so the test suite for Terraform won't necessarily capture subtle bugs that arise from running this every time.

Also, probably the cleanest way to apply a new .terragrunt configuration is to completely delete the .terraform folder and start from scratch, but we certainly wouldn't want to do that on every run b/c of all the extra bandwidth, there may be multiple modules to download, etc.

from terragrunt.

hmmmm - sounds like some middle ground is needed then, instead of going for a more complex solution (hashing .terragrunt), it should be pretty easy to add a terragrunt reload command that just re-runs terraform remote config when you know you've changed it

from terragrunt.

I like the idea of hashing .terragrunt, but I'm not keen on writing and managing extra files to maintain that hash. There is probably a fairly simple bug in this code that just needs a second look.

Whatever solution we go with, the terragrunt reload command sounds like a good idea to have as a backup.

from terragrunt.