feat(symbols): derive the upload endpoint from --base-uri

[abelonogov-ld]

Summary

Uploading symbols to anything other than production took two flags that had to agree: --base-uri to name the instance, and --backend-url to name that same instance's observability API. Staging looked like this:

ldcli symbols upload --type android --project my-project \
  --base-uri https://ld-stg.launchdarkly.com \
  --backend-url https://pri.observability.ld-stg.launchdarkly.com \
  --access-token api-...

The second flag is derivable from the first. Every instance publishes its observability API under a host named for the instance, which is exactly how the production default in this file was already built, so --backend-url now defaults to the API of whichever instance --base-uri names and the command above loses a line.

Only LaunchDarkly's own hosts are derived from. A base URI aimed at a local stack or a proxy says nothing about where its observability API listens, so those keep today's production default, and --backend-url still overrides everything — which is how local development already points at http://localhost:8082/private.

Behavior for the default base URI is unchanged: app.launchdarkly.com derives the same pri.observability.app.launchdarkly.com the constant held. The flag's registered default moves from that constant to empty so the derivation can run; --help now names the production URL in the description instead.

Test plan

• go test ./cmd/symbols/ — new TestDefaultBackendURLFor covers production, staging, a regional host, trailing slashes and whitespace, and the cases that fall back to the default (local stack, a host that merely ends in the domain name, unset, unparseable)
• go build ./...
• Uploaded Android symbols to staging with only --base-uri https://ld-stg.launchdarkly.com. A staging access token authenticated, which it could not have against the production default, so the derivation reached the staging API. The mapping was keyed by the pg_map_id R8 recorded and the dedup handshake reported the index already stored there, so the handshake round-tripped but the object PUT did not re-run

Made with Cursor

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 1dec099. Configure here.}

[cursor]

Silent backend default change

Medium Severity

When --backend-url is unset, uploads now derive the observability endpoint from --base-uri for LaunchDarkly hosts, changing the previous production default for non-prod instances with no transitional stderr notice. That violates the rule that user-facing CLI default changes need a warning for at least one release cycle.

Additional Locations (1)

• cmd/symbols/upload.go#L744-L745

 

^{Triggered by learned rule: Breaking CLI default changes require transitional stderr warnings}

^{Reviewed by Cursor Bugbot for commit 1dec099. Configure here.}