vscode-apimanagement
vscode-apimanagement copied to clipboard
microsoft
VS Code extension for Azure API Management.
This is used when communicating to the management API of APIM All versions prior to 2021-08-01 are deprecated and will be phased out starting 1st June 2024. This is documented...
Does this occur consistently? Repro steps: 1. 2. Action: azureApiManagement.setApiFilter Error type: MissingOrIncorrectVersionParameter Error Message: API version query parameter is not specified or was specified incorrectly. Supported versions: 2021-08-01,2021-12-01-preview,2022-04-01-preview,2022-08-01,2022-09-01-preview,2023-03-01-preview,2023-05-01-preview,2023-09-01-preview Example...
I am new to Visual Studio Code, new to the Visual Studio Code API Management Extension, and new to Azure API Management, so I am _really_ new. When using the...
From official announcement, all API versions for the Azure API Management service prior to 2021-08-01 are being retired by June 2024. [API version retirements (June 2024)] (https://learn.microsoft.com/en-us/azure/api-management/breaking-changes/api-version-retirement-sep-2023) But this extension...
Does this occur consistently? Yes Repro steps: 1. Selected VS Code API management extension 2. Selected the subscription for which I wanted to create the API management. 3. clicked create....
Any insight? Error logs: From client: initialize({"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"apim-policy","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en","supportsProgressReporting":true,"supportsInvalidatedEvent":true,"supportsMemoryReferences":true,"supportsArgsCanBeInterpretedByShell":true,"supportsMemoryEvent":true,"supportsStartDebuggingRequest":true}) To client: {"seq":0,"type":"response","request_seq":1,"command":"initialize","success":true,"body":{"supportsConfigurationDoneRequest":true,"supportsRestartRequest":false,"supportsRestartFrame":false}} From client: launch({"type":"apim-policy","request":"launch","name":"Attach to APIM","stopOnEntry":true,"gatewayAddress":"wss://aipm-epso-authtest01.azure-api.net/debug-0123456789abcdef","managementAddress":"https://management.azure.com//subscriptions/e0ba1ef1-afb6-4f98-9d74-a71e310bae84/resourceGroups/epso-apimauth-test-rg/providers/microsoft.apimanagement/service/aipm-epso-authtest01","subscriptionId":"e0ba1ef1-afb6-4f98-9d74-a71e310bae84","operationData":"GET https://aipm-epso-authtest01.azure-api.net/demo/topics HTTP/1.1\nOcp-Apim-Subscription-Key: xxxxxx\nOcp-Apim-Debug: xxxxxx\nOcp-Apim-Trace: true\n","fileName":"aipm-epso-authtest01-demo-conference-api-GetTopics.http","__sessionId":"206d4c9a-0b26-4464-a081-a09851634617"}) To client: {"seq":0,"type":"event","event":"output","body":{"category":"stderr","output":"Can't connect to gateway: Unexpected server...
Hi team, the policy step through debugging tool is awesome. It however, seems to be affected by the new behavior around tracing and debugging in APIM. We see this [discussed...
Please add OData APIs. At this point they are skipped by the extension. This ensures live debugging of policies can be done.
I am using Azure API Management plugin version 1.0.9 with VS Code. When editing an API using the OpenAPI Editor, the URL scheme gets reset to "https" no matter what...
Editing a named value is a pain in the rear presently. I'd love to see that behavior updated from the current one-line textbox to loading it in the editor like...
