Azure / Azure/azure-rest-api-specs
[Question] Why does Application Gateway on the Portal support Keyvault Certificates but the API/CLI/etc only support Secret ID
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
### API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/53bed2dccf392c14a412735c38a0f55645812294/specification/network/resource-manager/Microsoft.Network/stable/2022-07-01/applicationGateway.json
### API Spec version
2022-07-01
### Question/Query
The Azure Portal allows use to use a Certificate from Key Vault against an App Gateway (and APIM), however the API only allows a `Secret_Id` from Key Vault, NOT a certificate.
This makes things a bit of a nightmare from a certificate renewal point of view, because we now have to change it in two places
### Environment
_No response_
Contributor guide
Research direction
Start with the linked specification/network/resource-manager/Microsoft.Network/stable/2022-07-01/applicationGateway.json and inspect the Application Gateway Key Vault certificate fields. Compare the portal's certificate behavior with the API's Secret_Id-only shape, then determine the expected API change and acceptance criteria with the service owners. Done requires a decided contract that supports the intended certificate renewal workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, openapi
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100