Configuring digger.yml

Set up digger.yml for OpenTofu, Terraform, or Terragrunt projects using explicit or generated project definitions

Use this page to configure digger.yml after your smoke test passes.

Prerequisites:

• Set up your OpenTaco account
• Set up GitHub App
• PR Automation Smoke Test

Choose your configuration model

You can define projects explicitly, or generate projects automatically for larger monorepos.

OpenTofu

Explicit projects

projects:
- name: core
  dir: infra/core
  opentofu: true
- name: app
  dir: infra/app
  opentofu: true

Generated projects

generate_projects:
  include: "infra/**"
  terragrunt: false
  opentofu: true

Terraform

Explicit projects

projects:
- name: core
  dir: infra/core
- name: app
  dir: infra/app

Generated projects

generate_projects:
  include: "infra/**"
  terragrunt: false

Terragrunt

Explicit projects (small repos)

projects:
- name: dev
  dir: dev
  terragrunt: true
- name: prod
  dir: prod
  terragrunt: true

Generated projects with blocks (recommended for monorepos)

generate_projects:
  blocks:
    - block_name: dev
      terragrunt: true
      root_dir: "dev/"
      workflow: default
    - block_name: prod
      terragrunt: true
      root_dir: "prod/"
      workflow: default

workflows:
  default:
    plan:
      steps:
        - init
        - plan
    apply:
      steps:
        - init
        - apply

Validate digger.yml

• Keep dir paths relative to repository root.
• Use stable project names because project names appear in comments and logs.
• Start with a small set of projects, then expand once plan/apply behavior is confirmed.

For advanced project generation patterns, see Generate Projects.

Next step

Continue with Configuring the GitHub Actions workflow.