Add ability to define extra deps for local modules

[erpel]

Pull Request

Related Github Issues

• .json files support ? #243

Description

I'm looking to add the ability to also trigger a run based on non-terragrunt files in local modules referenced via source in the terraform block in terragrunt.hcl.
Especially the filename is up for discussion. It seems obvious to name it terragrunt.hcl, but I'm not sure if I got an overview of all possible implications of adding such a file local modules that should not be applied directly.

Looking for feedback, it seems to be working for us in a small experimental run.

Security Implications

• [none]

System Availability

• [none]

[Almenon]

I'm not really clear on the difference in behavior between this and the existing extra_atlantis_dependencies. You can do this already with the existing functionality. In extra_atlantis_dependencies you can specify a path to a file in your modules directory.

[Almenon]

Also ignore the CI test error, sorry, #311 will fix it. This PR will need to be rebased once that is merged in.

[erpel]

Thanks for taking the time to look at this.

I'm not really clear on the difference in behavior between this and the existing extra_atlantis_dependencies. You can do this already with the existing functionality. In extra_atlantis_dependencies you can specify a path to a file in your modules directory.

This is basically meant as a convenience thing. Right now, if the module is used in 7 locations in my repo, I'd need to duplicate the extra_atlantis_dependencies statement in every terragrunt.hcl that references that module.
This change would increase separation of concerns, making it possible to use such a local module without having to know about or care for the inner workings of these modules and their "special files".

I've been testing it locally with the env vars patch from #311 applied, was unsure if I should duplicate it in here to show tests are green. Thanks for clarifying the preferred strategy. Will take care of a rebase if interest in this feature is expressed.

[erpel]

@Almenon The pipeline is green currently. Would you consider this again?