ghost
commented
1 year ago Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @toddysm, @luisdlp, @northtyphoon.
Issue Details
When using a rust crate autogenerated from the [containerregistry data-plane API definition](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/containerregistry/data-plane/Microsoft.ContainerRegistry/preview/2019-08-15/containerregistry.json ) I'm having issues with the server requiring ApiVersion to be specified. I can see that the [resource-manager](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/stable/2022-12-01/containerregistry.json#L27) API definition has ApiVersion parameters and the corresponding auto-generated rust crate does pass in the api version parameter correctly. I would have expected https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/openapi-authoring-automated-guidelines.md#r2015-parameternotdefinedinglobalparameters to cover this case. Is there something I'm missing here that means api version isn't required and if so how can I persuade the server of that?
| Author: | dsteeley |
|---|---|
| Assignees: | - |
| Labels: | `Container Registry`, `Service Attention`, `needs-triage` |
| Milestone: | - |
When using a rust crate autogenerated from the containerregistry data-plane API definition I'm having issues with the server requiring ApiVersion to be specified.
I can see that the resource-manager API definition has ApiVersion parameters and the corresponding auto-generated rust crate does pass in the api version parameter correctly.
I would have expected https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/openapi-authoring-automated-guidelines.md#r2015-parameternotdefinedinglobalparameters to cover this case.
Is there something I'm missing here that means api version isn't required and if so how can I persuade the server of that?