You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a981b5b
Browse filesBrowse the repository at this point in the historyBrowse files
fix(rpc): route --network through the enable prompt when Tooling Access is off (DX-6132) (#55)
The --network lane resolved the per-network URL map in ensure_networks
before reaching the enable-recovery flow, so an account that hadn't
enabled Tooling Access hit a hard 'endpoint did not report an id' error
instead of the enable gate the default lane offers.
ensure_networks now checks status.enabled and, when off, routes through
the existing maybe_enable gate (TTY prompt / --yes auto-enable /
actionable error), re-fetches status, then requires the endpoint id. The
'did not report an id' error is reserved for the provisioned-but-idless
case. Reuses maybe_enable verbatim so gating matches the default lane.
Adds two tests: disabled + non-TTY without --yes fails with the enable
hint and makes zero enable/URL-fetch/RPC calls; disabled + --yes
enables, re-fetches, and routes to the mapped URL.
0 commit comments