Allow more flexibility in module registry versioning
A possible solution could be allowing partial tags or tags with wildcards in the Spacelift Registry. These special tags could dynamically point to the latest corresponding full SemVer tag. Some approaches that could work:
Allow defining versions without the full SemVer format, like
1.0(to allow any patch upgrade) or just1(to allow any minor upgrade)Introduce wildcard-like versions, such as
1.x.xor1.0.x, with a defined convention for the wildcard character.
Ultimately, Terragrunt is simply querying a URL like: https://app.spacelift.io/registry/modules/v1/account/module-name/provider/VERSION/download where VERSION is just a part of the path. Given that, this enhancement should be feasible.
This change would help working around Terragrunt’s strict module versioning and significantly reduce manual maintenance.
- Workaround
- N/A
- Problem
Log in to comment and vote
Comments1
Natalia Gazda
Mar 10, 2025
@Juan Vela Hi Juan, thanks for the post! I’m afraid we’re gonna reject it. We want to be consistent with registry standard, and we believe that should be handled by Terragrunt, not us. I hope you understand.