docs: add reference for new attest family of flags#1523
Merged
Conversation
Signed-off-by: Justin Chadwell <me@jedevc.com>
jedevc
force-pushed
the
docs-reference-attest
branch
from
7316755 to
4903f46
Compare
crazy-max
approved these changes
Jan 17, 2023
Member
|
Looks like this was cherry-picked in #1524, so removing the label again 😅 |
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
4 participants
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.
⬆️ Follow-up to docker/docs#16517
We should have a brief explanation in the reference of the new
--attest,--sbomand--provenanceflags, which can point to the manuals where we have a more complete write-up and explanation of how to use it.