$ defang config set DJANGO_SECRET_KEY=XXXXXXXX POSTGRES_PASSWORD=XXXXXXXX SSL_MODE=true --stack=azuredefangwus3
* Using the "azuredefangwus3" stack on azure from --stack flag and local stack file
* Updated value for SSL_MODE
* Updated value for DJANGO_SECRET_KEY
* Successfully set 2 config value(s)
To update the deployed values, do:
defang --stack=azuredefangwus3 compose up
Error: failed to put Key Vault secret: PUT https://kv-xxxxxxxx.vault.azure.net/secrets/Defang--crewai--azuredefangwus3--POSTGRES-PASSWORD
--------------------------------------------------------------------------------
RESPONSE 403: 403 Forbidden
ERROR CODE: Forbidden
--------------------------------------------------------------------------------
{
"error": {
"code": "Forbidden",
"message": "Caller is not authorized to perform action on resource.\r\nIf role assignments, deny assignments or role definitions were changed recently, please observe propagation time.\r\nCaller: appid=04b07795-8ddb-461a-bbee-02f9e1bf7b46;oid=15a56bb9-b5a8-47bc-b1b6-a1e62ca3508f;iss=https://sts.windows.net/12c0f515-fa47-402f-9982-de7646d3cb28/\r\nAction: 'Microsoft.KeyVault/vaults/secrets/setSecret/action'\r\nResource: '/subscriptions/7bbe3d56-ec33-4388-85ed-998ebc6299ab/resourcegroups/defang-crewai-azuredefangwus3-westus3/providers/microsoft.keyvault/vaults/kv-xxxxxxxx/secrets/defang--crewai--azuredefangwus3--postgres-password'\r\nAssignment: (not found)\r\nDenyAssignmentId: null\r\nDecisionReason: null \r\nVault: kv-xxxxxxxx;location=westus3\r\n",
"innererror": {
"code": "ForbiddenByRbac"
}
}
}
--------------------------------------------------------------------------------
So in case of the RBAC is not propagated yet: