Receiving RBAC related errors when creating key vault secrets through terraform

Question

As of yesterday, we started experiencing issues creating key vault secrets using terraform.

The account we are using has all the required permissions to be able to create key vault secrets.

We are experiencing the same when terraform tries to read the state for the key vault secrets.

If we keep retrying the create or read, it sometimes succeeds, which is why I don't believe this issue is related to permissions, otherwise it would always fail.

We are experiencing errors like the below:

making Read request on Azure KeyVault Secret my-secret: keyvault.BaseClient#GetSecret: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 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=xxx;oid=xxx;iss=https://sts.windows.net//\r\nAction: 'Microsoft.KeyVault/vaults/secrets/getSecret/action'\r\nResource: '/subscriptions//resourcegroup/xxx/providers/microsoft.keyvault/vaults/xxx/secrets/my-secret'\r\nAssignment: (not found)\r\nDenyAssignmentId: null\r\nDecisionReason: null \r\nVault: xxx;location=xxx\r\n" InnerError={"code":"ForbiddenByRbac"}

Are there any issues with RBAC and key vaults at this time?

Answer 1

Issue seemed to resolve itself.