Repository navigation
feat(plan): yodel plan --part writes the versioned plan as a chant change-set part (#237) - #272
Merged
Merged
Conversation
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.
Closes #237
yodel plan <env> --part <file>writes the versioned plan as a chant change-set part (plannersql), through the sql lexicon'ssqlVersionedPlanPart(chant 0.124.23). A chant Op reads it withreadChangeSetPart, joins it to other members' parts withcomposeChangeSet, and gates them together; a Cedar policy reads the result ascontext.plan.--json.yodel apply's gate binds. A plan apply would refuse is afailedmember.approvalpart writes the part against the server and checks chant reads it back as planned under the gate's digest.npm run claims -- approvalon this branch: ch and pg pass, both caught under BREAK=1.