Add local DocumentDB Quick Start design#653
Conversation
Signed-off-by: Guanzhou Song <guanzhousong@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds a UX design reference for the proposed Local Quick Start experience, documenting how the extension would install, start, connect to, and manage a local DocumentDB container from VS Code.
Changes:
- Adds end-to-end UX flows, tree shapes, lifecycle states, and action matrices.
- Documents conflict handling, Docker readiness, telemetry hints, edge cases, non-goals, and design review outcomes.
- Captures intended coexistence with the existing manual local connection flow.
|
@guanzhousongmicrosoft Have you had a chance to check out the wizard and container launch flow in the Postgres extension? |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Guanzhou Song <guanzhousong@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Guanzhou Song <guanzhousong@microsoft.com>
|
This is encouraging: microsoft/vscode#307838 |
|
I'm keen to drop all manual connections in the Everything else can be just added as a regular connection. Thoughts? |
xgerman
left a comment
There was a problem hiding this comment.
two more things to consider:
- users might use test containers which start a container before every test and then tear down after the test. In case of an error, they might choose to retain the container. How can we easily connect to that for investigations?
- how do we manage multiple containers running potentially multiple document DB versions or otherDBs?
I am also curious how we initialize the container. Are we relying on the init scripts or will be a special VS code thing? How would we support init script development?
Are we telling users when a new conatiner image becomes available or do we update automatically?
Lastly, if there's an issue with the container are we helping to file an issue in the documentdb repo?
- Add local-quickstart-v2.md: simplified design that removes the dedicated local connection subtree, uses a webview for container creation, gates TLS exceptions in the regular connection wizard, and migrates legacy emulator connections on first launch. - Mark local-quickstart.md as iteration 1 with a forward reference.
|
@guanzhousongmicrosoft @xgerman -- Iteration 2 of the design doc is here: local-quickstart-v2.md Key changes from iteration 1:
The iteration 1 doc is kept as reference with a forward pointer to this revision. |
…decision note - terminal-first create progress for v1.0 (staged in-webview card deferred to v1.1) - adopt @microsoft/vscode-container-client (Docker+Podman) as the runtime layer - port fallback only for the default port; read the bound port from docker inspect - distinguish create-vs-start failure; pre-check connection name AND container name - scope prereq checks v1.0/v1.1; add section 18.1 PostgreSQL source-benchmark learnings - add docs/ai-and-plans/PRs/653-local-quickstart-design/description.md decision note Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@xgerman — thanks for the review. The inline comments are all addressed in iteration 2 (
For context, there's a short decision/reasoning note for reviewers at |
✅ Code Quality Checks
This comment is updated automatically on each push. |
📦 Build Size Report
Download artifact · updated automatically on each push. |



Summary
Validation