Bicep deployment error v0.1.5

[Swi7chb1ade]

Using v0.1.5 of the script results in a deployment error

v.0.1.4 does not result in this error

Not using an existing Event hub

[cs-wayne-hsieh]

@Swi7chb1ade
Were you de-provisioning and re-deploying within a short amount time?

Root Cause

Azure will automatically re-create the EventHub instance if there are one or more existing or just deleted diagnostic settings pointing to the EventHub with default partition count 4.

The created EventHub namespace is a Standard namespace, which doesn't allow to change partition count after EventHub instance is created.

Solution

Azure usually need some time to propagate the result of creating/deleting resources. It would be better to wait for an hour to re-deploy after deprovision.

[Swi7chb1ade]

@cs-wayne-hsieh

No - the service was de-provisioned and then re-deployed 24hrs later. I spent a full day troubleshooting with v0.1.5, as soon as I switched to v0.1.4 the deployment was successful.