Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terraform provider updates #9747

Open
1 task done
ukv001 opened this issue May 16, 2024 · 1 comment
Open
1 task done

Terraform provider updates #9747

ukv001 opened this issue May 16, 2024 · 1 comment
Labels
L: github:actions GitHub Actions L: terraform Terraform packages T: feature-request Requests for new features

Comments

@ukv001
Copy link

ukv001 commented May 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Feature description

We have a repo that contains all our infra structure, separated into different environments. Under each environment we have 2 infra structures, one for the actual infra structure and one for uploading secrets to vault
e.g.
infrastructure/environments/dev/infrastructure
infrastructure/environments/dev/vault
infrastructure/environments/prod/infrastructure
infrastructure/environments/prod/vault
it seems that in the dependabot file I need to specifify each infrastructure
e.g. for dev/infrastructure

  • package-ecosystem: "terraform"
    directory: "infrastructure/environments/dev/infrastructure"
    schedule:
    interval: "daily"
  • package-ecosystem: "terraform"
    directory: "infrastructure/environments/dev/vault"
    schedule:
    interval: "daily"

From what I have experienced the other types of ecosystems I can just add the / and it will find files needed, e.g. for actions, and pom files and so on.

is this a flaw in the terraform or is it on purpose ? I do realise I would like to separate one environment out, so I can look at the plan for sure before applying.

@ukv001 ukv001 added the T: feature-request Requests for new features label May 16, 2024
@github-actions github-actions bot added L: github:actions GitHub Actions L: terraform Terraform packages labels May 16, 2024
@zahorniak
Copy link

Hi @ukv001,

Does a configuration like this not solve your problem?

updates:
  # To keep Terraform modules up to date
  - package-ecosystem: "terraform"
    directories:
      - "/infrastructure/environments/dev/infrastructure"
      - "/infrastructure/environments/dev/vault"
      - "/infrastructure/environments/prod/infrastructure"
      - "/infrastructure/environments/prod/vault"
    schedule:
      interval: "daily"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L: github:actions GitHub Actions L: terraform Terraform packages T: feature-request Requests for new features
Projects
Status: No status
Development

No branches or pull requests

2 participants