docs(witan): drop the direct-store-URI cutover alternative from the migration runbook - #260
Open
blarghmatey wants to merge 1 commit into
Open
docs(witan): drop the direct-store-URI cutover alternative from the migration runbook#260blarghmatey wants to merge 1 commit into
blarghmatey wants to merge 1 commit into
Conversation
…igration runbook The port-forward + raw bearer-token variant of the local-to-shared cutover used --target <URI> the same way every other migrate merge invocation does, but against a deployment that flag is refused outright (the destination is resolved server-side from the caller's own identity). Trying it against the production deployment during the go-live produced exactly that confusion. Removed the alternative and pointed at WITAN_TARGET as the only supported self-service path.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Witan migration runbook to discourage direct-store-URI cutovers.
Changes:
- Removes the cluster-credential port-forward subsection.
- Declares the
WITAN_TARGETMCP path as the supported self-service cutover route.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+254
to
+255
| **only supported way** to run this cutover: there is no direct-store-URI | ||
| alternative for it, on purpose — a port-forward + raw bearer token variant |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are the relevant tickets?
N/A
Description (What does it do?)
docs/migration-runbook.md's "If you have cluster credentials" subsection — a port-forward + rawOMNIGRAPH_BEARER_TOKENalternative to the self-service local-to-shared cutover.WITAN_TARGET-selected MCP path is now the only supported way to run this cutover, and why the direct-store-URI variant was removed.How can this be tested?
Read-through only — no code changes. Confirmed no other section links to or references the removed subsection (
grep -n "cluster credentials\|port-forward\|OMNIGRAPH_BEARER_TOKEN"against the file before/after).Additional Context
Found during the production go-live: passing
--target <the deployment's MCP URL>towitan migrate mergelooks like it should work the same way--targetworks everywhere else in the same command, butRemoteServerProxy.merge_storerefuses atargetargument outright once a deployment is selected (the destination is resolved server-side from the caller's own identity, not client-named). The removed subsection offered a second, direct-URI way to do the identical cutover and used that same--target <URI>shape, so it was a live source of the same confusion rather than a genuinely different tool for a genuinely different job.witan whoami --target <name>/witan login --target <name>already establish--target <name>meaning a named config target elsewhere in this CLI;migrate merge --targetis the one command where it still means a literal destination store URI. Unifying that is a real option (see the parallel thread on this in the current session) but out of scope for this docs-only fix.