generate_projects does not respect Terragrunt dependency order

[ZIJ]

If there are dependencies across auto-generated terragrunt projects, e.g. apps depend on VPC, then Digger does not run them in the correct order. The order of execution appears to be random or alphabetical. Likely a bug in terragrunt-atlantis-config lib that is used under the hood.

Workaround: use explicit project definition with terragrunt: true and depends_on: ["vpc", "rds"] options. Not ideal as it leads to duplication of dependency declarations.

[c-p-b]

A good way to reproduce this is to create a simple dependency configuration that looks like this setup: https://github.com/gruntwork-io/terragrunt-infrastructure-live-example

Then tell Digger to autogenerate:

generate_projects:
  terragrunt_parsing:
    parallel: false
    createProjectName: true
    createWorkspace: true
    defaultWorkflow: default
workflows:
  default:
    plan:
      steps:
        - init
        - plan
        - run: echo "Hello World"

Then try to resolve some (nonalphabetical) projects and note that it will not resolve them according to how terragrunt specifies them in dependency DAG

[ben-of-codecraft]

We had this reported today also, for backendless mode I think the only solutions I could think of was to all the ordering of impacted projects in digger.yml or enable a way to do run all in Terragrunt so the dependency map is built based on the dependencies block

What do you all think?