Azure-sdk-for-js: KeyPermissions is missing a value

Created on 19 Aug 2020  路  8Comments  路  Source: Azure/azure-sdk-for-js

https://github.com/Azure/azure-sdk-for-js/blob/f21b80dba999383946dc9f9705e1d5e507976e83/sdk/keyvault/arm-keyvault/src/models/index.ts#L613

The KeyPermissions, SecretPermissions, and CertificatePermissions types are missing the value all which is a possible value of access policy permissions when getting the key vault using the api and is supported by ARM template deployments.

Here is an example of an permissions of a access policy on a key vault that is returned by the api:

Permissions to Keys                        : {all}
Permissions to Secrets                     : {all}
Permissions to Certificates                : {all}
KeyVault Mgmt Service Attention customer-reported needs-team-attention question

All 8 comments

Hello, @CYoderDev

Thank you for reaching out to us!

This issue will require further investigation, but so far I can say that:

I'll come back with a better response later today, or perhaps tomrorow.

@CYoderDev Update:

The "all" value as a permission is not present in Azure's public API for Key Vault: https://github.com/Azure/azure-rest-api-specs/blob/a7ca142c3f0f290fdda778f26f4f1fab65f71cf9/specification/keyvault/resource-manager/Microsoft.KeyVault/stable/2019-09-01/keyvault.json#L979-L1059

I wonder what are we missing! I'm still in communications with my team. I'll report back as soon as I have an update.

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @RandalliLama, @schaabs, @jlichwa.

I've switched this issue to be a service-level issue. Hopefully we'll get more answers this way.

@jlichwa that looks cool! Thank you!

Closing issue as its been addressed.

Was this page helpful?
0 / 5 - 0 ratings