Azure / Azure/azure-rest-api-specs
issues with `Microsoft.Batch` data-plane enum values not matching values in practice
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
The spec for Microsoft.Batch data-plane has enums that don't match the values in practice.
* [TaskSchedulingPolicy.nodeFillType](https://github.com/Azure/azure-rest-api-specs/blob/e2ba2eded6ff0dda9894928981067b884d641462/specification/batch/data-plane/Microsoft.Batch/stable/2021-06-01.14.0/BatchService.json#L12287-L12294) shows "spread" and "pack", but in practice from the service, is "Pack" or "Spread".
* [NodePlacementPolicyType](https://github.com/Azure/azure-rest-api-specs/blob/e2ba2eded6ff0dda9894928981067b884d641462/specification/batch/data-plane/Microsoft.Batch/stable/2021-06-01.14.0/BatchService.json#L14043-L14050) shows "regional" and "zonal", but in practice from the service, is "Regional" or "Zonal".
* [IPAddressProvisioningType](https://github.com/Azure/azure-rest-api-specs/blob/e2ba2eded6ff0dda9894928981067b884d641462/specification/batch/data-plane/Microsoft.Batch/stable/2021-06-01.14.0/BatchService.json#L14273-L14280) shows "batchmanaged", "usermanaged", and "nonpublicaddresses". However, in practice from the service, is "BatchManaged", "UserManaged", and "NonPublicAddresses". Note, this spec entry shows "x-ms-enum" which provides a mapping for the value "batchmanaged" having the name "batchManaged", but neither of these are the value actually used in the service of "BatchManaged".
Contributor guide
Assessment
This issue has not been assessed yet.