Error az role assignment create --role "Key Vault Secrets Officer" --scope $K

CLI commands are not working about azure-pipelines-secrets-key-vault HOT 2 OPEN

kalmax commented on July 29, 2024

CLI commands are not working

from azure-pipelines-secrets-key-vault.

Comments (2)

triple-it commented on July 29, 2024

For example, the most outstanding change is that the objectId property in the output JSON of a Graph object is replaced by id.

Maybe the following will work?

# assign RBAC role to the current user to manage secrets
#USER_ID=$(az ad signed-in-user show --query objectId -o tsv)
USER_ID=$(az ad signed-in-user show --query id -o tsv)

and..

#SPN_ID=$(az ad sp list --display-name "spn-keyvault-devops" --query [0].objectId --out tsv)
SPN_ID=$(az ad sp list --display-name "spn-keyvault-devops" --query [0].id --out tsv)

from azure-pipelines-secrets-key-vault.

triple-it commented on July 29, 2024

Hi!
Not to disappoint you, but I have done a checkout, applied above patched, and did a re-run.

Downloading secrets using: https://keyvault021.vault.azure.net/secrets?maxresults=25&api-version=2016-10-01.
##[error]Get secrets failed. Error: Caller is not authorized to perform action on resource.

(Even with automatic SP and manual SP configuration in azure devops)

So this issue is not resolved for you yet... I suppose...
Did not investigate what could be the problem then

from azure-pipelines-secrets-key-vault.

Recommend Projects