You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here the single-keyvault environment has a dependency on the modules in the common-infra environment (specifically the keyvault). I need to obtain both the input config and output from the common-infra environment before deploying. I see ther are mock_outputs blocks for dependencies in terragrunt but is there also support for mock_inputs so the configuration from the other deployment is passed to this new terraform template environment?
Here is a sample terragrunt.hcl of the single-keyvault template
Hi! This is actually in our roadmap, but hasn't been implemented yet. We've had this commented in various conversations, but it is good to finally have an issue that formally proposes the need.
Here are the relevant past conversations I can recall:
I have a terraform template environment that is dependent on the inputs and outputs of various modules in a separate terraform template environment.
Here is the tree structure:
Here the
single-keyvault
environment has a dependency on the modules in the common-infra environment (specifically the keyvault). I need to obtain both the input config and output from thecommon-infra
environment before deploying. I see ther aremock_outputs
blocks for dependencies in terragrunt but is there also support formock_inputs
so the configuration from the other deployment is passed to this new terraform template environment?Here is a sample
terragrunt.hcl
of thesingle-keyvault
templateThe text was updated successfully, but these errors were encountered: