cli: use manifest reference values for attestation #608
Conversation
This file contains 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
burgerdev
reviewed
Jun 20, 2024
|
Could you make it so that |
Should be done in a separate PR. |
davidweisse
force-pushed
the
dav/use-manifest-ref-values
branch
from
593ea8c to
6ccecdb
Compare
burgerdev
approved these changes
Jun 21, 2024
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 changes the Coordinator validate options to use the reference values from the local manifest in the
setandverifycommand. The verify command takes an additional flag--manifestfor this to provide the path to the manifest.The default workspace directory for the
verifycommand is no longer./verify, because the manifest lies in the current directory. Instead, the output files for theverifycommand are always written to theverifydirectory in the current workspace directory.