feat(sawala): akuna storage status + isolate (org-level data residency)#95
Merged
Conversation
sawala akuna storage status — show whether the org uses a dedicated DB
sawala akuna storage isolate — enable a dedicated DB for the WHOLE org:
move all BYO connections onto it, new BYO
connections inherit it; managed stays shared
Org-level counterpart to the per-connection 'akuna connection isolate'
primitive, backed by /cli/akuna/storage{,/isolate}. Live-verified
against the deployed backend. Changeset included.
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
1 participant
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.
Org-level CLI parity for data residency, matching the
/storageendpoints (core #429).Commands
sawala akuna storage status→GET /cli/akuna/storage— shows shared vs dedicated-database, andn of mBYO connections on it.sawala akuna storage isolate→POST /cli/akuna/storage/isolate— enables a dedicated database for the whole org: moves all BYO connections onto it, new BYO connections inherit it, managed stays shared. Confirmation-gated (--yes/TTY),--dry-run, idempotent.The existing
sawala akuna connection isolate <id>stays as the per-connection primitive;storage isolateis the org-level counterpart (isolation is an org setting).Verified
Typecheck + esbuild build clean;
--helpregisters both. Live-tested against the deployed backend:Changeset included (
@sawala/climinor).