unable to map two replication networks using azure bicep
- Dominant language
- TypeScript
- Stars
- 108
- Forks
- 44
- Avg merge
- 18h 53m
- Merged PRs (30d)
- 29
Description
unable to map two replication networks using azure bicep.getting below error.
Status Message: Primary key property ArmResourceName is null in entity LookupByArmResourceNameInVault. (Code: BadRequest)
Primary key property ArmResourceName is null in entity LookupByArmResourceNameInVault. (Code:UnhandledException)
```bicep
resource NENWVNETMAP 'Microsoft.RecoveryServices/vaults/replicationFabrics/replicationNetworks/replicationNetworkMappings@2023-06-01' = {
parent:NERnetwork
name: 'norwayeast-norwaywest-vnet-mapping'
properties: {
recoveryNetworkId:recoveryNWNetworkId
fabricSpecificDetails: {
instanceType: 'AzureToAzure'
primaryNetworkId: recoveryNENetworkId
}
}
}
resource NWNEVNETMAP 'Microsoft.RecoveryServices/vaults/replicationFabrics/replicationNetworks/replicationNetworkMappings@2023-06-01' = {
parent:NWRnetwork
name: 'norwaywest-norwayeast-vnet-mapping'
properties: {
recoveryNetworkId:recoveryNENetworkId
fabricSpecificDetails:{
instanceType: 'AzureToAzure'
primaryNetworkId: recoveryNWNetworkId
}
}
}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the two Microsoft.RecoveryServices/vaults/replicationFabrics/replicationNetworks/replicationNetworkMappings resources using API version 2023-06-01 and inspect the ArmResourceName error. Compare the two mapping definitions and the corresponding Azure resource schema; done means both replication network mappings deploy successfully without the reported BadRequest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100