Using the Up CLI behind a corporate HTTP/HTTPS proxy — Git proxy with SSH auth for apiDependencies

Issue

• apiDependencies fail to fetch when outbound network access is restricted and traffic must go through a corporate HTTP/HTTPS (HTTP CONNECT) proxy

• Private Git repositories (internal CRDs / dependencies) are unreachable

• Affected commands: up dependency add, up dependency update-cache, up project build, up composition render, up test run

Environment

• Up CLI — fix available in v0.49.0 and later

• Spaces (Cloud / Self-Hosted)

• Corporate HTTP/HTTPS proxy (HTTP CONNECT); direct outbound blocked

• Private Git repositories accessed over SSH

Resolution

• Upgrade the Up CLI to v0.49.0 or later:

curl https://cli.upbound.io | sh
# or upgrade via Homebrew

• Use the --git-proxy flag to tunnel SSH over the HTTP CONNECT proxy when fetching Git-based dependencies

• Applies to the dependency-fetching commands (e.g. up dependency add, up project build, up composition render)

• Release notes: https://docs.upbound.io/reference/release-notes/up-cli/#v0490

Cause

• Up CLI versions before v0.49.0 had no way to tunnel Git dependency fetches through an HTTP CONNECT proxy

• With direct outbound access blocked, apiDependency fetches over SSH failed

• Resolved by --git-proxy support (SSH over HTTP CONNECT), shipped in v0.49.0