Describe the bug
running terragrunt validate or terragrunt run-all validate while using disable_init=true leads to an auth error for the http backend.
the disable_init works well if there are no dependencies in the terragrunt file but errors if the module has a dependency.
Expected behavior
disable_init should be used also for dependencies.
Versions
Terragrunt version: shipped version of the image
Terraform version: shipped version of the image
Environment details: alpine/terragrunt:1.4.4
Additional context/questions
isn't is simply possible to pass the -backend=false to terraform if provided for terragrunt?
am i doing something wrong? i even tried to use mock_outputs, sadly terraform still wants to init the backend.
is there a way to let terragrunt only "build" all the terraform files and manually change in the cache directory and run terraform validate -backend=false without requiring a working backend?
is there a way to mock the backend? i really don't want to use/access the production backend only to validate the syntax in the ci.
i also tried to hardcode disable_init=true to check if there is a problem with piping the TERRAGRUNT_DISABLE_INIT to the dependency. no luck.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for raising this issue.
Describe the bug running
terragrunt validate
orterragrunt run-all validate
while usingdisable_init=true
leads to an auth error for the http backend.the
disable_init
works well if there are no dependencies in the terragrunt file but errors if the module has a dependency.Expected behavior
disable_init
should be used also for dependencies.Versions
Additional context/questions isn't is simply possible to pass the
-backend=false
to terraform if provided forterragrunt
? am i doing something wrong? i even tried to usemock_outputs
, sadly terraform still wants to init the backend.is there a way to let terragrunt only "build" all the terraform files and manually change in the cache directory and run
terraform validate -backend=false
without requiring a working backend?is there a way to mock the backend? i really don't want to use/access the production backend only to validate the syntax in the ci.
i also tried to hardcode
disable_init=true
to check if there is a problem with piping theTERRAGRUNT_DISABLE_INIT
to the dependency. no luck.also tried to use
skip_outputs
, same result.code snippets parent file,
remote_state
section:working module (with this module everything works fine and i get no backend error):
but as soon as i have a dependency in the module i get the following error:
failing module:
workaround
my workaround is the following hack in the parent file:
while using the following in the child file:
another workaround would be to allow terragrunt to use the http backend but prefix the state files with
ci_