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

Container Registry API Version in SDK isn't available #795

Closed
tombuildsstuff opened this issue Oct 5, 2017 · 3 comments
Closed

Container Registry API Version in SDK isn't available #795

tombuildsstuff opened this issue Oct 5, 2017 · 3 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved.

Comments

@tombuildsstuff
Copy link
Contributor

👋

As mentioned in #794 - I've been trying to migrate us over to using v11 of the Azure SDK for Go. Unfortunately it appears the API Version used for Container Registry also isn't configured correctly:

containerregistry.RegistriesClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="NoRegisteredProviderFound" Message="No registered resource provider found for location 'westeurope' and API version '2017-10-01' for type 'registries'. The supported api-versions are '2016-06-27-preview, 2017-03-01, 2017-10-01, 2017-06-01-preview'. The supported locations are 'westus, eastus, southcentralus, westeurope, northeurope, uksouth, ukwest, australiaeast, australiasoutheast, centralindia, eastasia, japaneast, japanwest, southeastasia, southindia, brazilsouth, canadaeast, canadacentral, centralus, eastus2, northcentralus, westcentralus, westus2'."

Checking the Provider Registration status in the Portal (output) - it appears whilst this this API version is valid for the Resource Provider itself (as it's shown in the error message above) and some of the sub-types of the Resource Provider - isn't available for the registry type.

As such - would it be possible to downgrade to the previous version of the Container Registry API until this is fixed? I'm unsure if this needs a Swagger fix or a Generator fix - but at this point in time we're unable to upgrade to v11

Thanks!

@marstr
Copy link
Member

marstr commented Oct 6, 2017

Howdy @tombuildsstuff!

Looks like there were some timing issues for the v11 release. @djyou drew our attention to this PR this morning: Azure/azure-rest-api-specs#1771 which seems to have been merged in after our release. We'll be regening and releasing a patch to fix the Container Registry issues that you're seeing.

Sorry for the hassle!

-Martin

@marstr marstr added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Oct 6, 2017
@marstr
Copy link
Member

marstr commented Oct 6, 2017

This should be taken care of in #801

@mcardosos
Copy link
Contributor

Fixed

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved.
Projects
None yet
Development

No branches or pull requests

3 participants