-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix(terragrunt): wrong packageName resolution for GitLab, Bitbucket and Gitea datasources #28075
fix(terragrunt): wrong packageName resolution for GitLab, Bitbucket and Gitea datasources #28075
Conversation
…nd Gitea datasources
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
otherwise LGTM
Looking forward to this fix. Terragrunt dependencies from local VCS have been broken for the last four weeks. Existing PRs have been closed as well. |
🎉 This PR is included in version 37.322.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@lstoeferle I'm not sure, but is this handling self-issued tls certificates correctly? Can you confirm, this is working? |
Hi @mstoetzer-jambit, |
Unfortunately we had some errors:
|
Hi @mstoetzer-jambit, @viceice may I open another PR to remove the |
sure |
We are using SSH URI in terragrunt.hcl: terraform {
source = "git::ssh://git@gitlab.tld:2222/some-namespace/terraform-modules/aws-lb.git//alb?ref=1.1.0"
}
|
As a workaround you could try without terraform {
- source = "git::ssh://git@gitlab.tld:2222/some-namespace/terraform-modules/aws-lb.git//alb?ref=1.1.0"
+ source = "git::ssh://git@gitlab.tld:2222/some-namespace/terraform-modules/aws-lb//alb?ref=1.1.0"
} |
removed Renovate failed to look up the following dependencies: Failed to look up gitlab-tags package some-namespace/terraform-modules/k8s With Renovate Version
With that, we were able to fetch release notes correctly and dependency lookup was working |
Yes, the fix is provided here #28726. The |
Changes
Unfortunately I introduced a bug with my last PR for the
terragrunt
manager, which was released in v37.253.0.I had a look into the issue and found the problem. It seems the
GitLab
,Bitbucket
andGitea
datasources require only the path to the repository as a value for thepackageName
field (see here), where theGitTag
datasource requires the whole URL to the repository as value for thepackageName
field.Unfortunately I'm not able to test this on a real integration, but at least the unit-tests should cover the changes.
Additionally it seems these changes also fixed a wrongly configured unit-test for terragrunt sources with fixed IP address.
Context
#27903 (comment)
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: