Azure / Azure/azure-rest-api-specs
Storagecache (a.k.a HPCCache) less of `usageModel` enums
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
Currently, the `usageModel` used for [`Nfs3Target`](https://github.com/Azure/azure-rest-api-specs/blob/7e3bf6306c5ffd00b97a93870945fa5debd873af/specification/storagecache/resource-manager/Microsoft.StorageCache/stable/2021-03-01/storagecache.json#L1941) and [`blobNfsTarget`](https://github.com/Azure/azure-rest-api-specs/blob/7e3bf6306c5ffd00b97a93870945fa5debd873af/specification/storagecache/resource-manager/Microsoft.StorageCache/stable/2021-03-01/storagecache.json#L1967) are simple string(s). **It would be helpful to list the allowed value as enum in the Swagger,** from SDK users' POV.
Contributor guide
Research direction
Inspect specification/storagecache/resource-manager/Microsoft.StorageCache/stable/2021-03-01/storagecache.json at the Nfs3Target and blobNfsTarget definitions linked in the issue. Determine the allowed usageModel values from the API specification context, then represent those values as enums for both properties. Done means the Swagger documents the permitted values for SDK consumers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100