[codex] Move cloud secret values to WorkOS Vault#215
Draft
RhysSullivan wants to merge 2 commits intomainfrom
Draft
[codex] Move cloud secret values to WorkOS Vault#215RhysSullivan wants to merge 2 commits intomainfrom
RhysSullivan wants to merge 2 commits intomainfrom
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
executor-cloud | f288a36 | Apr 13 2026, 04:59 AM |
@executor/sdk
@executor/plugin-file-secrets
@executor/plugin-google-discovery
@executor/plugin-graphql
@executor/plugin-keychain
@executor/plugin-mcp
@executor/plugin-onepassword
@executor/plugin-openapi
@executor/plugin-workos-vault
commit: |
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 changed
This switches the cloud app to use WorkOS Vault for secret values and adds a dedicated
@executor/plugin-workos-vaultpackage.It also cleans up the cloud secrets UI so storage/provider implementation details are not exposed to users:
Why
Cloud secret values should live in WorkOS Vault, while the app should treat Vault as a simple value store.
The previous implementation wrote app-managed registry state into Vault, which made the integration more complex than necessary. This change keeps secret refs/metadata in Postgres-backed KV and uses Vault only for secret values.
Impact
Root cause
The initial Vault integration used Vault for both value storage and app-level registry metadata, which created unnecessary coupling and leaked implementation details into the product UI.
Validation
bun run --filter='@executor/plugin-workos-vault' testbun run --filter='@executor/cloud' typecheckbunx vitest run --config vitest.unit.config.ts(fromapps/cloud)