renovate/lib/modules/manager/terragrunt
2023-02-19 12:43:48 +00:00
..
__fixtures__ refactor: lib/modules (#14488) 2022-03-04 09:04:02 +01:00
__snapshots__ test: use jest v29 (#17151) 2022-08-16 14:22:29 +02:00
common.ts refactor: enums to unions (#18747) 2022-11-05 09:12:03 +00:00
extract.spec.ts refactor: strict manager tests (#16155) 2022-06-20 17:05:39 +02:00
extract.ts refactor: PackageFile -> PackageFileContent (#20502) 2023-02-19 12:43:48 +00:00
index.ts fix(manager/terragrunt): prevent overwriting versioning of GithubTags datasource (#19782) 2023-01-12 08:04:14 +00:00
modules.spec.ts refactor: strict manager tests (#16155) 2022-06-20 17:05:39 +02:00
modules.ts refactor: enums to unions (#18747) 2022-11-05 09:12:03 +00:00
providers.ts refactor: enums to unions (#18747) 2022-11-05 09:12:03 +00:00
readme.md docs(manager/terragrunt): fix wrong config (#19192) 2022-11-30 14:48:49 +01:00
types.ts refactor(manager): more strict null checks (#15168) 2022-04-20 06:19:59 +02:00
util.spec.ts refactor: enums to unions (#18747) 2022-11-05 09:12:03 +00:00
util.ts refactor: enums to unions (#18747) 2022-11-05 09:12:03 +00:00

Currently by default, Terragrunt support is limited to Terraform registry sources and GitHub sources that include SemVer refs, e.g. like github.com/hashicorp/example?ref=v1.0.0.

You can create a custom versioning config to support non-SemVer references. For example, if you want to reference a tag like module-v1.2.5, a block like this would work:

{
  "terragrunt": {
    "versioning": "regex:^((?<compatibility>.*)-v|v*)(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)$"
  }
}

Pinned Terragrunt dependencies like the following will get a PR whenever there is a newer version available:

terraform {
  source = "github.com/hashicorp/example?ref=v1.0.0"
}