Azure / Azure/azure-rest-api-specs
Microsoft.ContainerRegistry/registries resource have `Classic` listed as available `sku` although it has been deprecated.
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
Reported in: [Azure/bicep#4577](https://github.com/Azure/bicep/issues/4577)
The `Classic` Sku for Azure Container Registry has been deprecated but it's still listed in the swagger definition as allowed value.
https://github.com/Azure/azure-rest-api-specs/blob/b49af808cba06f45b01193623ce1ff9e2e017777/specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/preview/2021-06-01-preview/containerregistry.json#L3960-L3980
Contributor guide
Research direction
Open specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/preview/2021-06-01-preview/containerregistry.json around lines 3960-3980 and review the allowed sku values against the deprecation report in Azure/bicep#4577. Done means the Azure Container Registry specification no longer lists Classic as an available sku.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100