Support for nested terraform code and directories

[BhagyaAmarasinghe]

Is there an existing issue for this?

• [X] I have searched the existing issues

Feature description

Package Ecosystem

terraform

Description

When adding dependabot for terraform repositories with multiple nested directories:

• Dependabot will not look recursively through all directories for .tf files. And this prevents submodules from getting updates
• Also, in a repo where there are multiple directories, will result in having to create dependabot entries for every single directory which result in a very long file. It would be nice if we can implement a feature to use glob patterns or to provide multiple paths to dependabot directory so that it will pick the .tf files in the nested directories.

[HorizonNet]

@BhagyaAmarasinghe How does your Dependabot configuration and directory structure look like? I have a repository, where I also have nested modules in different sub-directories (multiple levels deep), and the following configuration just works fine.

---
version: 2
updates:
  - package-ecosystem: "terraform"
    directory: "/"
    schedule:
      interval: "daily"
      time: "07:00"
      timezone: "Europe/Berlin"

Please note that every module has a versions declaration in it, similar to the following

terraform {
  required_version = "~> 1.9.0"

  required_providers {
    azuread = {
      source  = "hashicorp/azuread"
      version = "2.53.1"
    }
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "3.110.0"
    }
  }
}

On a Dependabot run every single module gets updated within a single PR.

An alternative, if you want to handle directories differently or in groups, you can also use the directories configuration as outlined here.