You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Printing the manifest on successful verification doesn't provide much utility in communicating the output and can be extremely lengthy with larger directory trees.
A possible alternative is to print a summary listing the total number of hashed files, the number of verified files and (if verification has failed) a number of unverified files.
The text was updated successfully, but these errors were encountered:
--print is intended to both verify the manifest and print JSON so it can be used in a pipeline and guarantee that you're only using validated data:
$ filepack verify --print | some-other-function
That being said, I'd like to support more user friendly output for filepack verify, so I'll hijack this issue title to reflect that.
casey
changed the title
Replace --print option for filepack verify with user-friendly output
More user friendly output from filepack verifyNov 11, 2024
In the meantime additional documentation to clarify the usage of --print would be ideal, whether it is documented in man pages or in external documentation.
Printing the manifest on successful verification doesn't provide much utility in communicating the output and can be extremely lengthy with larger directory trees.
A possible alternative is to print a summary listing the total number of hashed files, the number of verified files and (if verification has failed) a number of unverified files.
The text was updated successfully, but these errors were encountered: