Replies: 1 comment
-
Hi,
References: https://terragrunt.gruntwork.io/docs/reference/config-blocks-and-attributes/#dependency https://terragrunt.gruntwork.io/docs/reference/config-blocks-and-attributes/#inputs |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi. I have a big Terraform codebase deploying resources to Azure.
I have the following structure:
I would like to migrate to Terragrunt soon as it would enable me to have DRY code and different configuration for each environment, which at the moment is injected via Azure DevOps variables when the pipeline starts.
However I have a problem:
In my main.tf I have the following:
As you can see, the provider configuration depends on the output of
aks
module that creates the Kubernetes cluster.The Helm provider configuration is then passed on to each module with the providers block, as
cert_manager
module shows.How do I generate the Helm provider configuration dynamically given this setup?
I thought I might need to refactor so that I have a
aks_configuration
module where I configure the provider and then pass this on to the modules likecert_manager
using Helm provider, then when migrating to Terragrunt, I could write aprovider.hcl
inside aks_configuration.I am not sure it is the right way of doing things though. What do you suggest?
Beta Was this translation helpful? Give feedback.
All reactions