From a107eefc80eea509c875e1f1e1041888536fc5c6 Mon Sep 17 00:00:00 2001 From: Eugene <70693118+MrLutik@users.noreply.github.com> Date: Wed, 22 Nov 2023 20:35:24 +0100 Subject: [PATCH] docs: Add Documentation for --yes Flag in Blob Signing (#274) * Add yes flag desc Signed-off-by: mrlutik * Fix typo in shell command Signed-off-by: mrlutik * Add backticks to the flag representation in description Co-authored-by: ltagliaferri Signed-off-by: Eugene <70693118+MrLutik@users.noreply.github.com> --------- Signed-off-by: mrlutik Signed-off-by: Eugene <70693118+MrLutik@users.noreply.github.com> Co-authored-by: ltagliaferri --- content/en/signing/signing_with_blobs.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/en/signing/signing_with_blobs.md b/content/en/signing/signing_with_blobs.md index 764bf94b..4a371640 100644 --- a/content/en/signing/signing_with_blobs.md +++ b/content/en/signing/signing_with_blobs.md @@ -96,3 +96,10 @@ You can sign it with the normal `cosign sign` command and flags: ```shell $ cosign sign gcr.io/user/demo/artifact ``` +## Non-Interactive Signing with the Yes Flag + +In situations where automated signing is required, such as within CI/CD pipelines, the `--yes` flag becomes essential. This flag, when used with signing commands, bypasses any confirmation prompts, enabling a smooth, uninterrupted signing process. This is particularly crucial in automated environments where manual input isn't feasible. The `--yes` flag ensures that your signing operations can proceed without manual intervention, maintaining the efficiency and speed of your automated workflows. + +``` +cosign sign-blob --yes -key cosign.key myregistry/myimage:latest +``` \ No newline at end of file