Drift configurable separately per project

[ZIJ]

From the user:

... if there’s a way to specify in the digger.yaml file which projects should be checked for drift.

also ... if it’s possible to define multiple drift workflows and assign each one to a specific type of project. For example, we have a terraform/aws_devel/** project that includes everything related to AWS development, same with Prod ... and another environments, each has its own aws_access_key and aws_secret.

What we’d like to do is have something like an aws_devel_drift.yaml that only checks for drift in the devel projects, and the same for prod, pre, demo, etc.

[motatoes]

I think there needs to be the ability to specify several filters in the drift workflow - mainly by project name in the custom digger workflow file.

something like:

    - name: digger drift detection
      uses: diggerhq/digger@vLatest
      with:
        ee: 'true'
        mode: drift-detection
        drift-filters: |
          paths:
            - infra/**                  # include
            - '!infra/**/.terraform/**' # exclude
            - '!infra/prod/experimental/**'
          projects: ['prod-*', 'eu-*']
        setup-aws: true
        setup-terragrunt: true
        setup-terraform: true
        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        no-backend: true

The behaviour would be that any project who's properties match the filter patterns is included in projects to perform drift on. Unless it is explicitly excluded by the "!" exclude flag.

So in example above the directories would be included:

infra/prod/vpc
infra/prod/security

And following would not be included

infra/dev/vpc
infra/prod/expermintal