cli/verify: expose latest transition on verify#2187
Open
davidweisse wants to merge 1 commit intomainfrom
Open
Conversation
burgerdev
reviewed
Feb 19, 2026
475e720 to
d6fdaad
Compare
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.
This returns the
LatestTransitionobject oncontrast verifyand writes the latest transition hash to theverifydirectory. Obtaining the signature of the latest transition is a prerequisite for recovering the Coordinator config map history. The transition hash can be used duringcontrast setto disallow updates to an unknown Coordinator state.Returning the transition hash here is not strictly necessary as it can be recomputed using the manifest history already returned by
contrast verifybut this makes it easier and allows, e.g., passing a transition hash directly per command line flag duringcontrast set.We don't write the signature to the verify directory. I'm currently planning on integrating the config map recovery into the
verifysubcommand, since in this step we get everything we need to reconstruct the config map history, so there is no need for the user to see the signature.