From 4c41296bc5e3547355b97472a61fc04901499010 Mon Sep 17 00:00:00 2001 From: Jinhong Brejnholt Date: Thu, 9 Jun 2022 15:38:24 +0200 Subject: [PATCH] Updated Azure kms commands. (#1972) Use "--kms" instead of "-kms", and used "--key" instead of "-key", as the single dash is deprecated. Signed-off-by: Jinhong Brejnholt Author: Jinhong Brejnholt Date: Tue Jun 7 21:30:42 2022 +0200 Co-authored-by: Jinhong Brejnholt --- KMS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/KMS.md b/KMS.md index a17a8db3703..97f42f32879 100644 --- a/KMS.md +++ b/KMS.md @@ -138,9 +138,9 @@ The following environment variables must be set to let cosign authenticate to Az - AZURE_CLIENT_ID - AZURE_CLIENT_SECRET -To create a key using `cosign generate-key-pair -kms azurekms://[VAULT_NAME][VAULT_URI]/[KEY]` you will need a user which has permissions to create keys in Key Vault. For example `Key Vault Crypto Officer` role. +To create a key using `cosign generate-key-pair --kms azurekms://[VAULT_NAME][VAULT_URI]/[KEY]` you will need a user which has permissions to create keys in Key Vault. For example `Key Vault Crypto Officer` role. -To sign images using `cosign sign -key azurekms://[VAULT_NAME][VAULT_URI]/[KEY] [IMAGE]` you will need a user which has permissions to the sign action such as the `Key Vault Crypto User` role. +To sign images using `cosign sign --key azurekms://[VAULT_NAME][VAULT_URI]/[KEY] [IMAGE]` you will need a user which has permissions to the sign action such as the `Key Vault Crypto User` role. ### Hashicorp Vault