Azure / Azure/azure-rest-api-specs
azure signalR is still updating even though the provisioning status shows succeeded.
Open
Nobody has claimed this yet.
Service Attention
SignalR
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 6k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 432
Description
When deleting the signalR custom certificate/ domain, the resource can't be deleted because the parent siganlR resource is still in updating status, despite of the "succeeded" provisioning status returned by the API (409 conflict error).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the Azure SignalR specification for custom certificate or domain deletion, then trace how the API reports provisioning and updating states around the 409 conflict; done means the relevant specification accurately reflects the observed deletion behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100