Help with SSH and HTTPS authentication for private Bitbucket repositories

[chrome cairn]

Hey, I need some help accessing our private Bitbucket repositories.
I have tried authentication with both SSH and HTTPS, but neither was successful.

With SSH authentication, I think we are hitting an edge case since our Bitbucket SSH service is available on a non-standard port (7999).
SSH_AUTH_SOCK is correctly configured (I can fetch the repository within the Dagger engine container), but when Dagger tries to fetch it, the port is removed. Based on the Dagger code, I think this conflicts with how the GitHub user is currently handled—the port is filtered out as a username from the URL before fetching the repository (ssh://[e-mail]:7999/scm/project/repo → ssh://[e-mail]).
Is there any workaround to use the port? I tried configuring port in ssh/config without success.

With HTTPS authentication, I just can't figure out how to configure it in the Dagger engine container. I tried manually configuring .gitconfig and git-credentials, but it seems that the credentials are not being used. Based on the logs, the username is taken from /etc/gitconfig, but authentication fails regardless of how git-credentials is configured.
Is there any documentation on how to set up HTTPS authentication when the Dagger engine is manually started as a container?

[chrome cairn]

Issue with SSH authentication using non standard ssh ports is that the port is ignored when ref url is broken down.
https://github.com/dagger/dagger/blob/main/core/schema/modulesource.go#L311
By updating modulesource.go code to also append port if defined when modPath is being constructed solves the problem.

[waxen tree]

hey @chrome cairn nice finding. Any chance you're willing to submit a PR for it? 🙏

[waxen tree]

that's strange... the .gitconfig approach should work

if you can run git clone https://$uri from your CWD, running the dagger CLI should have the same effect from the git credential loading perspective

[chrome cairn]

Yes I can prepare one.

[chrome cairn]

I'm running dagger-engine separtely. Is there any configuration (env, mount) that I'm missing for this to work?

[waxen tree]

no, the .gitconfig credentials get loaded client side and passed to the engine

[waxen tree]

by client-side I mean relative to the CWD of the dagger client

[chrome cairn]

Aha, good to know. I will look into it - i was trying to configure this somehow on dagger-engine side. I was able to pull the repo locally, but I might have some non-standard setup for this to work out of the box.