Mandatory query parameters shown as template parameters when created from OpenAPI specification

Bug description

Setting a required “Query” parameter in OpenAPI is getting set as “Template” parameter in Azure APIM.

Reproduction steps

1. In the below OpenAPI sample, id has been marked as a required parameter in query :
2. On save of the OpenAPI spec, the mandatory query param is getting mapped to template param.
3. The main issue is that if the end user doesn’t provide an id in this above example, they would get a 404 resource not found without any additional info instead of a 400 Bad Request.

Expected behavior

Mandatory query parameters in OpenAPI spec should be created as mandatory query parameters and not template parameters. This behavior is happening if the api is created manually using the “Add operation” (without from OpenAPI spec).

Is your portal managed or self-hosted?

Managed

[t-angelman]

@mikebudzynski

As far as I understood the bugfix should have been rolled out. But we still experience this issue in Azure Portal API Management. Please clarify if that bugfix really had effect on that issue.

[mikebudzynski]

@Kumar-Ashwin-Hubert, the fix will be included in the next API Management service release in June and we expect it to fully roll out in July. You can monitor this GitHub site for the release notes: https://aka.ms/apim/releases Apologies for the confusion.