Azure / Azure/azure-rest-api-specs
CDNs REST API documentation lacks using "Latest" version from Key Vault when using custom domain with custom certificate
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
When configuring custom domain / HTTP / certificate via the Azure Portal, the UI suggests to set it to 'Latest' to always use the latest version of the certificate stored in Key Vault.
I don't see that this is possible via the REST API:
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cdn/resource-manager/Microsoft.Cdn/stable/2020-09-01/examples/CustomDomains_EnableCustomHttpsUsingBYOC.json
https://docs.microsoft.com/en-us/rest/api/cdn/cdn/customdomains/enablecustomhttps#keyvaultcertificatesourceparameters
Contributor guide
Research direction
Start with specification/cdn/resource-manager/Microsoft.Cdn/stable/2020-09-01/examples/CustomDomains_EnableCustomHttpsUsingBYOC.json and the linked enablecustomhttps Key Vault certificate source parameters documentation. Compare both with the Azure Portal's “Latest” option; done means the REST documentation clearly explains whether and how the latest Key Vault certificate version is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100