#terragrunt (2022-01)
Terragrunt discussions
Archive: https://archive.sweetops.com/terragrunt/
2022-01-12
![zadkiel avatar](https://secure.gravatar.com/avatar/ac34df8afa3827c17e9894bf6b169137.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0008-72.png)
Hey there! I have a situation where terragrunt auto-init executes all the time, even if the module is already initialized and nothing changed since the last init. Are you experiencing the same kind of behavior? I found this issue that may be related and will add details to it asap. https://github.com/gruntwork-io/terragrunt/issues/1742 Thank you.
A customer reported that they were running into issues with plugin caching being ignored because terragrunt was rerunning init.
2022-01-19
![Kartik V avatar](https://secure.gravatar.com/avatar/f6975e8bf541803a68265018b24696b0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0020-72.png)
Hello everyone , I am trying to achieve vpc cross region peering using terragrunt need some ideas/suggestion to use provider as alias in terragunt.hcl root
![Kyle Johnson avatar](https://avatars.slack-edge.com/2021-06-15/2171990287941_5f6b14681e8198b0b932_72.png)
since the hcl file can’t use a provider alias, I’ve had to use one of two approaches:
• separate terragrunt modules which different provider output (no alias required!)
• making a “wrapper” terraform module which expects certain providers to exist (don’t pass as terragrunt inputs, but instead create the two providers with terragrunt) it’s messy either way