This message was deleted.

Hi John, sorry I haven’t heard about anything like this before. Do you have any log output that could help narrow down the bottleneck? For example if i run the example repo with

--log-level=info

i’ll get some timestamps as it goes through different phases:

--log-level=info
time="2023-09-05T10:40:37-04:00" level=info msg="Detected Terragrunt directory at ./examples/terragrunt/"
time="2023-09-05T10:40:37-04:00" level=info msg="Starting: Downloading Terraform modules"
time="2023-09-05T10:40:37-04:00" level=info msg="Starting: Evaluating Terraform directory"
time="2023-09-05T10:40:37-04:00" level=info msg="Starting: Downloading Terraform modules"
time="2023-09-05T10:40:37-04:00" level=info msg="Starting: Evaluating Terraform directory"
time="2023-09-05T10:40:37-04:00" level=info msg="Starting: Retrieving cloud prices to calculate costs"

Hi Tim, thanks for the reply! This is the raw output from the GoCD job, it's a bit long so put it in a snippet. You can see that the

Detected Terragrunt directory

phase takes a significant amount of time and so do a couple of the evaluation phases:

Ok let me ask around

Thank you!

Ok, so the first suggestion is to try writing a config file. This should help with the project detection phase. Second, it we could see debug logs (

--log-level=debug

) that may help narrow it down a bit more.

A config file is already used:

version: 0.1
projects:
  - name: ${TG_DIR} hive
    path: ${TG_DIR}
    exclude_paths:
      - test-server/*
    env:
      ENV: hive
      ACCOUNT_NAME: hive
      REGION: us-east-1

Thanks John. I’m not really seeing anything obvious, it just seems to be slow, even the terragrunt evaluation. Best guess is that it’s hitting some cpu or memory bottleneck.