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

terragrunt catalog - hosting: "self-hosted.gitlab.com" is not supported yet #3800

Open
j2udev opened this issue Jan 22, 2025 · 1 comment · May be fixed by #3867
Open

terragrunt catalog - hosting: "self-hosted.gitlab.com" is not supported yet #3800

j2udev opened this issue Jan 22, 2025 · 1 comment · May be fixed by #3867
Assignees
Labels
contributions-requested Requesting contributions from the community enhancement New feature or request preserved Preserved issues never go stale

Comments

@j2udev
Copy link

j2udev commented Jan 22, 2025

Describe the bug

I'll open by saying this may not be a bug as the error message clearly states it's not supported yet... but opening on the off chance it's just being overlooked. When trying to plug our private, self-hosted gitlab registry into the catalog command (and likely the scaffold command, but I haven't tested). I get an error like this:

terragrunt catalog --root-file-name=root.hcl
15:35:32.429 INFO   Terragrunt Cache server is listening on 127.0.0.1:58105
15:35:32.430 INFO   Start Terragrunt Cache server
15:35:32.435 INFO   Cloning repository "git::https://my-self-hosted.gitlab.com/my-group/terraform/meta?ref=main" to temporary directory "/tmp/catalog4d474a6d6732674d7a5a4e565f7658416230364d36756f44367a45/meta"
15:36:05.673 INFO   Shutting down Terragrunt Cache server...
15:36:05.673 INFO   Terragrunt Cache server stopped
15:36:05.674 ERROR  hosting: "my-self-hosted.gitlab.com" is not supported yet
15:36:05.674 ERROR  Unable to determine underlying exit code, so Terragrunt will exit with error code 1

Our private repo, meta, is a meta repo of terraform modules that exist under a modules directory as git submodules. I'm not sure that's affecting anything, but it's worth calling out.

Steps To Reproduce

It's a little hard to reproduce I'd say... you'd need to self host a private gitlab registry and if the error couldn't be recreated that way... you'd maybe need to also create a meta repo of your terraform modules.

Expected behavior

I expect that I can use terragrunt catalog/scaffold using our private, self-hosted gitlab instance.

Versions

  • Terragrunt version: 0.72.3
  • OpenTofu/Terraform version: tofu: 1.7.0
  • Environment details (Ubuntu 20.04, Windows 10, etc.): Ubuntu Noble in a devcontainer running on an arm64 M1 Mac
@j2udev j2udev added the bug Something isn't working label Jan 22, 2025
@yhakbar yhakbar self-assigned this Jan 31, 2025
@yhakbar yhakbar added preserved Preserved issues never go stale enhancement New feature or request contributions-requested Requesting contributions from the community and removed bug Something isn't working labels Jan 31, 2025
@yhakbar
Copy link
Collaborator

yhakbar commented Jan 31, 2025

I would classify this as an enhancement, rather than a bug.

I've marked it as preserved and requesting community contributions, as it's not complicated, but not a high priority to tackle right now.

You can see an example of how we handled this for Enterprise GitHub here:
https://github.com/gruntwork-io/terragrunt/blob/main/cli/commands/catalog/module/repo.go#L140-L155

I don't have a self hosted server of GitLab to test this against, so I would ask for good faith confirmation from anyone that does pick this up that they'll do adequate testing, and document in the codebase that this is maintained on a best effort basis by the community.

@j2udev j2udev linked a pull request Feb 10, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contributions-requested Requesting contributions from the community enhancement New feature or request preserved Preserved issues never go stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants