Eliminate a failure path for Sigstore and show softcoded verify path
What does this MR do and why?
The example code for cosign verify contains a double forward slash in the path - which looks like an error to the average eye.
Since the input path to cosign is completely hidden by the built-in GitLab support for cosign, the user does not have the source to see that the double forward slash is both expected and required to get a valid verification.
Additionally, since the source path is not visible, an example of a softcoded verify path is also not known.
This MR:
- makes a special note that the double forward slash is expected and required.
- makes note of the error that results when a single slash is used.
- shows an example of a softcoded path for
cosign verify
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.