feat: sync org-local bindings for cross-org promotion#46
Merged
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
4 tasks
shuaib-ahmed-vapi
approved these changes
Jul 22, 2026
Contributor
Author
Merge activity
|
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.

Linear ticket
https://linear.app/vapi/issue/PRISM-978/gitops-support-cross-org-resource-migration-with-uuid-reference
Value
Customers can now bootstrap each org's credential and phone-number bindings into its gitignored environment file. This lets the same logical configuration move between orgs without copying secrets or hard-coding another org's UUIDs.
This PR provides the binding-discovery foundation and a complete dummy dev → staging → production example. The promotion command remains a separate deliverable under PRISM-978.
Evidence of value
API Changes (including webhooks + events)
Is this changing the public API?
If yes, is it backward‐compatible?
Non backward-compatible changes might break customers' agents. Please proceed with care and notify the team.
Testing plan
npm run build.node --import tsx --test tests/bindings.test.ts.npm test; the current repository baseline is 265 passing and 20 known hash-store/migration failures, with no new failures from this change..env.<org>block without provisioning resources.