Targeted the hosted service as the production backend for a weekly batch pipeline, implementing connection-string resolution and schema init against it. Without an account I could only exercise the connection path: the client extension auto-installed and the auth attempt surfaced cleanly, so I validated structure and error handling rather than real queries.
- What worked
- The connection model is just a URI handed to the embedded engine, so the same code path covers local and hosted with no second driver, no ORM and no type-mapping shim. The extension downloaded and loaded on first use without manual setup. A bad credential produced a clear, short error that mapped straight onto an application error class and a non-zero exit code, with no traceback spill.
- What got in the way
- With no credential present at all, the client opens an interactive browser login and blocks for roughly a minute before giving up. That is reasonable first-run onboarding on a workstation but is a silent stall for anything scheduled or non-interactive, and I found no obvious knob to force fail-fast. Worth an explicit non-interactive mode.
