Using dependencies within non-default ports

[mPokornyETM]

Hi All, At first big thanks to this tool. It is amazing. I used it in my open source tools (on github) to share the knowledge with other users and it works perfectly.

Now I am trying to using that in our Azure DevOps repository and I have some troubles.

When I understand it correctly this shall works:

dependencies:
  apm:
    - git: https://<host>:8443/tfs/<org>/<team>/_git/core-knownledge-hub

But the apm install says "Failed to clone repository .... "
The interesting thing is this output:

cmdline: git clone -v --depth=1 -- https://<host>/tfs/<org>/<team>/_git/core-knownledge-hub /tmp/tmplpmztrhb
....
fatal: unable to access 'https://<host>/tfs/<org>/<team>/_git/core-knownledge-hub'

As you can see (and this is not typo) the port is missing in the URL.
How shall I proceed in this case. It is a bug? Or do I something wrong.

Thx

Alot again

[danielmeppiel]

This is a known bug on which we are working here - #665

@edenfunf is leading the charge there, tagging you here

[edenfunf]

Thanks for the report! Confirmed — the port is stripped in two separate places: _normalize_ssh_protocol_url drops it for ssh:// URLs, and .hostname silently drops it for https:// URLs.

Working on a fix that preserves the port in the host field for both cases (e.g. host = "myserver:8443"), so the lockfile naturally reflects the actual source URL without needing any extra fields. Will update #665 once ready.

[mPokornyETM]

Great, thanks for the answer. Feel free to ping me, when I can help somehow.

[edenfunf]

Hi @mPokornyETM , this is now fixed via #665 .

What landed

Custom git ports on https://, http://, and ssh:// dependency URLs are now captured as a first-class port field on DependencyReference and threaded through every clone URL builder. The port survives in the apm.lock.yaml entry and is reused across protocol fallbacks, so a failed SSH attempt falls back to an HTTPS URL that keeps the same port instead of silently dropping it to the default 443.

Quick example

# apm.yml
dependencies:
  apm:
    - https://git.internal:8443/team/standards.git     # string form
    - git: https://git.internal:8443/team/repo.git     # object form
      ref: v1.0
    - git: ssh://git@bitbucket.example.com:7999/project/repo.git   # SSH with custom port
      ref: main

The lockfile records the port alongside the host:

dependencies:
  - repo_url: team/standards
    host: git.internal
    port: 8443
    resolved_commit: <sha>
    ...

Two things worth knowing

1. Use the ssh:// form for custom SSH ports. The SCP shorthand git@host:port/... is ambiguous — the : in that syntax is the path separator, so git@host:7999/repo is parsed as path 7999/repo, not port 7999. Always write ssh://git@host:7999/owner/repo.git when you need a custom SSH port.
2. Port is reused across both protocols on fallback. If your server serves SSH and HTTPS on different ports (e.g. Bitbucket Datacenter defaults: SSH 7999 / HTTPS 7990), the HTTPS fallback will hit an SSH-only port and fail loudly with a protocol error rather than silently routing to port 443 and reaching a different service. If this causes real pain, we can add separate ssh_port / https_port object-form fields — happy to open a follow-up if you run into it.

Thanks for the detailed report on the discussion — the HTTPS-port half of the PR. If you have any questions, feel free to discuss anytime.