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
I am currently using terragrunt v0.58.4 and when running terragrunt run-all plan --terragrunt-non-interactive -lock=false -refresh=false --terragrunt-include-external-dependencies --terragrunt-working-dir AWS_ACCOUNT_LEVEL I am getting the following errors:
* Failed to execute "terraform plan -input=false -lock=false -refresh=false" in ./eu-central-1/modor/services/ecr/.terragrunt-cache/yI628hksBOF_VVtNo2V1vj5toE8/eWIUFDSY^RB#X8Dom0nJ14Prazg
╷
│ Error: failed to read schema for aws_ecr_lifecycle_policy.this in registry.terraform.io/hashicorp/aws: failed to instantiate provider "registry.terraform.io/hashicorp/aws" to obtain schema: timeout while waiting for plugin to start
│
│
╵
This happens just with some resources. The resources themselves have no change to be performed. When running in the target directory the same terrargunt arguments everything is fine. If I do this for all affected resources (directory paths) and re-run terragurnt on the AWS account level everything works as expected.
I have not found this kind of issues in the github issues or online. Also I do not experience this in a different infrastructure with the same versions *69 / *72
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am currently using terragrunt v0.58.4 and when running
terragrunt run-all plan --terragrunt-non-interactive -lock=false -refresh=false --terragrunt-include-external-dependencies --terragrunt-working-dir AWS_ACCOUNT_LEVELI am getting the following errors:This happens just with some resources. The resources themselves have no change to be performed. When running in the target directory the same terrargunt arguments everything is fine. If I do this for all affected resources (directory paths) and re-run terragurnt on the AWS account level everything works as expected.
I have not found this kind of issues in the github issues or online. Also I do not experience this in a different infrastructure with the same versions *69 / *72
All reactions