Bug CNAME SWA
- Dominant language
- No language data
- Stars
- 346
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Custom domain stuck in "Deleting" state on Azure Static Web Apps.
The domain was added via the portal and failed with
"An unknown error has occurred while adding your custom domain."
A delete was then issued and completed with terminal provisioning
state 'Failed' (ResourceOperationFailure). The resource still reports
status "Deleting" with the original ADD error message, and no delete
operation is in flight.
DNS was verified correct and propagated before and after: a single
CNAME pointing to the app's default hostname, no A/TXT conflict at
that name, no CAA records on the zone, confirmed on two resolvers.
Attempted with no effect: portal delete, az staticwebapp hostname
delete, ARM REST DELETE and PUT across several api-versions.
Only one Static Web App exists across all subscriptions in the tenant.
Request: force-remove the stuck customDomains child resource so the
domain can be added again. Happy to share subscription and resource
IDs privately.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Azure portal, az staticwebapp hostname delete, and ARM REST DELETE/PUT paths described in the report, along with the customDomains child resource and its provisioning states. Done means the stuck resource is force-removed and the custom domain can be added again without the original ADD error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- backend-api-design, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100