Event Hub Disaster Recovery Config deployment 2024-01-01 version fails
- Dominant language
- TypeScript
- Stars
- 108
- Forks
- 44
- Avg merge
- 18h 53m
- Merged PRs (30d)
- 29
Description
**Bicep version**
0.28.1
**Describe the bug**
I'm trying to deploy two event hub namespaces with a disaster recovery config. Both event hubs are being successfully deployed with the latest API version (`2024-01-01`). When deploying the disaster recovery config with the same API version, it fails with the following error:
> No HTTP resource was found that matches the request URI 'https://westeurope-arm-dr.messaging.azure.net:10443/subscriptions/SUBSCRIPTIONID/resourcegroups/RESOURCEGROUPNAME/providers/Microsoft.EventHub/namespaces/PRIMARYEVENTHUBNAMESPACE/disasterRecoveryConfigs/PRIMARYEVENTHUBNAMESPACE?api-version=2024-01-01'.
Note that when changing the disaster recovery config deployment to version `2023-01-01-preview` it works again.
**To Reproduce**
- Deploy a primary event hub namespace with the latest API version (`2024-01-01`)
- Deploy a secondary event hub namespace with the latest API version (`2024-01-01`)
- Deploy a disaster recovery config with the latest API version (`2024-01-01`)
**Additional context**
We want to use the `2024-01-01` version for our event hub deployment because the failover to the secondary namespace is being done with the `Azure.ResourceManager.EventHubs` nuget package (version `1.1.0`) which uses by default the latest API version (`2024-01-01`).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the deployment with Event Hub namespaces and the disaster recovery config at API version 2024-01-01, then compare it with 2023-01-01-preview. Check the reported ARM request URI and determine whether the 2024-01-01 disaster recovery endpoint is supported; done when the deployment works with the required version or the incompatibility is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100