Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft.KeyVault/vaults/secrets declares support for 2020-04-01-preview, but the service does not allow it #11929

Closed
anthony-c-martin opened this issue Dec 3, 2020 · 11 comments
Assignees
Labels
KeyVault Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@anthony-c-martin
Copy link
Member

ARM returns the following message when attempting to PUT a Microsoft.KeyVault/vaults/secrets resource at version 2020-04-01-preview:

No registered resource provider found for location 'uksouth' and API version '2020-04-01-preview' for type 'vaults/secrets'. The supported api-versions are '2014-12-19-preview, 2015-06-01, 2016-10-01, 2018-02-14-preview, 2018-02-14, 2019-09-01'. The supported locations are 'northcentralus, eastus, northeurope, westeurope, eastasia, southeastasia, eastus2, centralus, southcentralus, westus, japaneast, japanwest, australiaeast, australiasoutheast, brazilsouth, centralindia, southindia, westindia, canadacentral, canadaeast, uksouth, ukwest, westcentralus, westus2, koreacentral, koreasouth,
francecentral, australiacentral, uaenorth, southafricanorth, switzerlandnorth, germanywestcentral, norwayeast, eastus2euap, centraluseuap'

This version is not supported in the RP manifest. Either the Microsoft.KeyVault service should add support for it, or remove the declarations for any unsupported APIs at this version.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 3, 2020
@ghost
Copy link

ghost commented Dec 22, 2020

Hi, anthony-c-martin. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

@ghost ghost added the no-recent-activity label Dec 22, 2020
@anthony-c-martin
Copy link
Member Author

Hi, anthony-c-martin. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

@markcowl - looks like something is up with the bot as this isn't a PR! Would you mind taking a look?

@ghost ghost removed the no-recent-activity label Dec 22, 2020
@zhenglaizhang zhenglaizhang added KeyVault Service Attention Workflow: This issue is responsible by Azure service team. and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Dec 29, 2020
@ghost
Copy link

ghost commented Dec 29, 2020

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

Issue Details

ARM returns the following message when attempting to PUT a Microsoft.KeyVault/vaults/secrets resource at version 2020-04-01-preview:

No registered resource provider found for location 'uksouth' and API version '2020-04-01-preview' for type 'vaults/secrets'. The supported api-versions are '2014-12-19-preview, 2015-06-01, 2016-10-01, 2018-02-14-preview, 2018-02-14, 2019-09-01'. The supported locations are 'northcentralus, eastus, northeurope, westeurope, eastasia, southeastasia, eastus2, centralus, southcentralus, westus, japaneast, japanwest, australiaeast, australiasoutheast, brazilsouth, centralindia, southindia, westindia, canadacentral, canadaeast, uksouth, ukwest, westcentralus, westus2, koreacentral, koreasouth,
francecentral, australiacentral, uaenorth, southafricanorth, switzerlandnorth, germanywestcentral, norwayeast, eastus2euap, centraluseuap'

This version is not supported in the RP manifest. Either the Microsoft.KeyVault service should add support for it, or remove the declarations for any unsupported APIs at this version.

Author: anthony-c-martin
Assignees: markcowl
Labels:

KeyVault, Service Attention

Milestone: -

@ruowan
Copy link
Member

ruowan commented Dec 29, 2020

Hi, anthony-c-martin. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

@markcowl Mark Cowlishaw FTE - looks like something is up with the bot as this isn't a PR! Would you mind taking a look?

Thanks for feedback. It's a bot issues. We have fixed it.

@sebansal
Copy link
Contributor

sebansal commented Jan 5, 2021

@jlichwa to help with triaging

@jlichwa
Copy link
Contributor

jlichwa commented Jan 5, 2021

@anthony-c-martin can you clarify. ARM returns the following message when attempting to PUT a Microsoft.KeyVault/vaults/secrets is a call to data plane with available versions: 7.0, 7.1. https://docs.microsoft.com/en-us/rest/api/keyvault/setsecret/setsecret

2020-04-01 is management plane version. With available for secrets only through ARM.

Is that makes sense?

@anthony-c-martin
Copy link
Member Author

@jlichwa - this issue report is concerning management plane (ARM), not data plane.

Here the KeyVault swagger spec declares support for operations on secrets through the ARM control plane with API version 2020-04-01-preview:

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.KeyVault/vaults/{vaultName}/secrets/{secretName}": {

The ARM control plane does not actually support this API with the declared API version.

@jlichwa
Copy link
Contributor

jlichwa commented Jan 5, 2021

@anthony I was able to reproduce it. I will work with engineering team.

@tyeth
Copy link

tyeth commented Mar 24, 2021

Hey @jlichwa any progress on this?

Is there a running list of incomplete api versions, or should we just not use any preview API versions until they make it out of preview?

@jlichwa
Copy link
Contributor

jlichwa commented Oct 29, 2021

@anthony-c-martin it seems like this issue is fixed.

@anthony-c-martin
Copy link
Member Author

@jlichwa, thanks for confirming! Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
KeyVault Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

8 participants