Azure / Azure/azure-rest-api-specs

App Service Certificate Order Certificate never completes the async operation

Open
#16,804 5 comments 1 reaction 0 assignees View on GitHub
App Services customer-reported question Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 2h
Merged PRs (30d)
424

Description

The endpoint `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CertificateRegistration/certificateOrders/{certificateOrderName}/certificates/{name}` is marked with `"x-ms-long-running-operation": true`: https://github.com/Azure/azure-rest-api-specs/blob/4946dbb5b2893a77ce52d08e2a855056e1acd361/specification/web/resource-manager/Microsoft.CertificateRegistration/stable/2021-02-01/AppServiceCertificateOrders.json#L470

However, the `provisioningState` property of the resulting resource to never gets to `Succeeded` (as described in https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations#provisioningstate-values). Instead, it stays in "Initiazed" ~forever.

A sample response:

```
{"id":"/subscriptions//resourceGroups/rg-test/providers/Microsoft.CertificateRegistration/certificateOrders/cert-order-my-domain-io/certificates/my-domain-io","name":"my-domain-io","type":"Microsoft.CertificateRegistration/certificateOrders/certificates","location":"global","properties":{"keyVaultId":"/subscriptions//resourcegroups/rg-test/providers/microsoft.keyvault/vaults/kv-test","keyVaultSecretName":"my-domain-io","provisioningState":"Initialized"}}
```

Expected: `"provisioningState":"Succeeded"`
Alternatively, consider removing the `x-ms-long-running-operation` annotation.

Contributor guide

Open the contributing guide

Research direction

Start with specification/web/resource-manager/Microsoft.CertificateRegistration/stable/2021-02-01/AppServiceCertificateOrders.json at the certificate endpoint and inspect its x-ms-long-running-operation annotation and provisioningState behavior. Compare the endpoint with the Azure async-operations guidance; done means either the resource reaches Succeeded or the long-running-operation annotation is removed, as confirmed by the resulting response.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, openapi
Domain
api, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.