Repository navigation
Vault: connect Organization runtime secrets on macOS - #530
annavesela wants to merge 1 commit into
Conversation
Add explicit workstation onboarding using fresh technical accounts and the existing own-vault custody. Select the module Organization at runtime without adopting a personal login or a hosted handover. Keep provider pre-allowance and installed-product qualification explicit.
|
Merge freeze on The candidate v0.1.13-rc.1 is |
|
The merge freeze for v0.1.13 is lifted. |
agentrozjedemeai
left a comment
There was a problem hiding this comment.
Prosím zachovejte diagnostiku nedostupného vaultu na nepodporovaných pracovních stanicích. declaredSecretsFinding nyní u každé organizační aplikace na workstation vrací prázdný nález (src/modules/runtime-secrets.ts:243–247), ale readVaultContext připojení na Linuxu nadále bezpodmínečně odmítá (src/vault/host.ts:92–94). Na linuxové stanici proto katalog označí aplikaci s povinným klíčem jako spustitelnou a doctor neohlásí známou příčinu; teprve pokus o spuštění skončí runtime-secret-unavailable. U volitelného klíče zmizí také diagnostická poznámka. Před touto změnou katalog tyto stavy uváděl. Prosím rozlište platformy tak, aby se dynamický výběr použil na macOS a nepodporované stanice si zachovaly nález workstation, a pokryjte povinný i volitelný klíč regresním testem katalogu/diagnostiky.
— Pablo
Status: ready for review (source and native candidate). Not deployed; installed consumer acceptance remains open.
A local Organization application can declare an optional runtime key, but the vault previously refused every workstation before reading it. This adds explicit macOS onboarding for a fresh, separate technical account per Organization and selects that account from the module's declared Organization at each start. A missing connection keeps optional-key applications usable without their provider capability.
The operator runs
vault connect-workstation --folder … --organization … --server … --name …. This records non-secret metadata and prints the generated account for the service administrator to pre-allow.setup,status,refreshandenvaccept the same selectors. Existing own-vault registration, credential custody, synchronization and secret parsing remain the only credential path. Disconnect removes local admission without deleting the remote vault; already running applications must be stopped to retire supplied keys. Hosted admission and Personalspace isolation remain intact.The design and failure contract are in
docs/workstation-vault.md. There is no human-account import, browser-session extraction, environment-file fallback, invented hosted handover or legacy-launcher workaround. This is CLI onboarding; the workstation's generic Vault page still has no Organization selector. Linux workstation onboarding is not enabled. The catalog defers Organization workstation admission to the dynamic source at start.Validation:
dfda0d2309657c5cdaec9d6728b59a8bbc6522ba; SHA-256f35f9c62d5b1d8115c2e1b1823d44cf74cfbda417c0d303ed0fa68ef0eeef03e. Native smoke passed CLI initialization/profile update, embedded HTML, authenticated API admission and graceful shutdown with development runtimes excluded from PATH. This is an unattested development candidate, not an installed product or live provider proof.Deployment remains bounded by the separate legacy-Folder migration and product activation contracts. Live service pre-allowance and a designated provider test have not happened. This PR does not close #313's installed consumer acceptance.
Work context: DEV-6631, branch
codex/DEV-6631-workstation-vault, owner-scoped productionspace worktree. Codex on a native macOS arm64 workstation. Exact local session and machine locators remain in the private sidecar rather than this public product repository.Refs #313.