-
Notifications
You must be signed in to change notification settings - Fork 39
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
VS Code extension 'Azure API Management' no longer able to connect after setting API version to 2021-08-01 #317
Comments
Could you please help understand how are you setting the API version in vscode extension. 2021-12-01-preview 2019-12-01 vscode-apimanagement/package-lock.json Line 22 in 60ac759
Will create a backlog item to upgrade to latest version. |
Thanks @annaji-msft for your feedback. We do not set the API version in the VS Code extension but in the Azure APIM service. Technically we are doing this via Terraform with the following code snippet:
We set this "min_api_version" as this was a recommendation shown in the Azure portal. To me it seems that the VS Code extension uses a version older that 2021-08-01. Maybe this line https://github.com/microsoft/vscode-apimanagement/blob/master/src/constants.ts#L33C24-L33C44 defines to use the API version 2019-01-01. |
I saw that there was a recent release which adds compatibility to API version 2019-12-01 (https://github.com/microsoft/vscode-apimanagement/releases/tag/1.0.7). Based on this post https://learn.microsoft.com/en-us/azure/api-management/breaking-changes/api-version-retirement-sep-2023 I was expecting a release that updates the API version to 2021-08-01 or later. @annaji-msft: Are you planning another release of the VS code extension in September? |
After setting the API version to 2021-08-01, the VS Code extension 'Azure API Management' is no longer able to connect.
Please see the attached screenshot. What API version is used by the VS Code extension and are there any plans to support the current stable versions of the API? Please note that there are already a version 2022-08-01 (GA) and 2023-03-01 (preview) available.
The text was updated successfully, but these errors were encountered: