Open TheWolfNL opened 5 years ago
Hm, that seems odd... What version of Terragrunt?
Upon some further investigation the problem seems to originate in the version check.
since the terragrunt's apply-all
doesn't use the config file, setting the TERRAGRUNT_CONFIG
will allow you to continue, but will then get stuck a bit later.
Running: terragrunt apply-all --terragrunt-non-interactive --terragrunt-working-dir test/dir
[terragrunt] [test] 2019/01/28 13:10:46 Running command: terraform --version
[terragrunt] 2019/01/28 13:10:46 Reading Terragrunt config file at test/dir/../terraform.tfvars
[terragrunt] [test] 2019/01/28 13:10:46 Initializing remote state for the gcs backend
[terragrunt] [test] 2019/01/28 13:10:46 Running command: terraform init -backend-config=bucket=terraform-test-state -backend-config=prefix=. -backend-config=project=terraform
Terraform initialized in an empty directory!
The directory has no Terraform configuration files. You may begin working
with Terraform immediately by creating Terraform configuration files.
[terragrunt] 2019/01/28 13:10:46 Running command: terraform @
Usage: terraform [-version] [-help] <command> [args]
@brikis98 Terragrunt version v0.17.4
Output when adding TERRAGRUNT_DEBUG='true':
Dir structure:
I'm running this with the working-dir because I want to apply everything inside the
test/dir
but apparently since the stack notescli/cli_app.go:214
that means thatapply-all
isn't properly recognised as a Multi-command.isMultiModuleCommand(command)
incli/cli_app.go:211
.