fix(workspace): honor explicit --workspace-id before requiring current workspace context

[jlaneve]

Problem

When authenticating non-interactively with an organization-scoped (workspace-operator) API token via ASTRO_API_TOKEN, commands like astro deployment variable update fail with:

Error: failed to find a valid workspace: failed to get current Workspace: current workspace context not set,
you can switch to a workspace with
	astro workspace switch WORKSPACEID

Passing --workspace-id <id> does not prevent the error — the flag is silently ignored on this path.

Root cause

coalesceWorkspace() called workspace.GetCurrentWorkspace() first and returned its error before ever consulting the --workspace-id flag:

wsFlag := workspaceID
wsCfg, err := workspace.GetCurrentWorkspace()   // called first
if err != nil {
    return "", errors.Wrap(err, "failed to get current Workspace")  // returns here — flag never consulted
}
if wsFlag != "" { return wsFlag, nil }           // flag only honored after

An org-scoped token has no workspaceId claim, so in a fresh CI home checkAPIToken leaves c.Workspace empty. GetCurrentWorkspace() then errors, and because the flag is checked after, --workspace-id cannot rescue it. This is deterministic given an empty current-workspace context (it only looks intermittent because a prior astro workspace switch may have persisted a workspace).

Fix

Return an explicit --workspace-id before calling GetCurrentWorkspace(), making the flag authoritative in non-interactive flows. This covers every command routed through coalesceWorkspace (deployment variable update, deployment objects, worker queues, deploy, dbt, env, inspect) — not just variable update.

Tests

Adds TestCoalesceWorkspace covering:

• explicit flag with no current context (the regression — fails before this change)
• explicit flag precedence over an existing context
• fallback to the current workspace context when no flag is provided
• error when neither source is available

Workaround (pre-fix)

astro workspace switch <id> first persists c.Workspace, after which the command succeeds. Confirmed still valid on affected versions.

🤖 Generated with Claude Code

[coveralls-official]

Coverage Report for CI Build 27781374546

Coverage increased (+0.007%) to 45.098%

Details

• Coverage increased (+0.007%) from the base build.
• Patch coverage: 7 of 7 lines across 1 file are fully covered (100%).
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	56373
Covered Lines:	25423
Line Coverage:	45.1%
Coverage Strength:	8.0 hits per line

---

💛 - Coveralls