Role assignment existence check in containerRegistry.bicep

[aazherelyeu]

Emailed to Matthew some time ago about this issue.

After successfully running of the IPAM deployment, if it's reran again you will encounter the following issue:

New-AzSubscriptionDeployment : 12:42:11 PM - The deployment 'ipamInfraDeploy-20241018124054PM' failed with error(s). Showing 1 out of 1 error(s).
Status Message: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details. (Code: DeploymentFailed)
 - The role assignment already exists. (Code:RoleAssignmentExists)

The bicep (containerRegistry.bicep) needs to be updated with a check for role assignment existence.

Please let me know once the bicep is updated.

[DCMattyG]

Hi there @aazherelyeu, apologies for the delay in my response on this item. I have made the changes in the code for the next version of Azure IPAM (v3.5) and I'm testing everything now. The new version should be available soon, thank you so much for bringing this issue to my attention.

[DCMattyG]

Hi @aazherelyeu, this has now been addressed with the release of Azure IPAM v3.5.0

Release Notes: https://github.com/Azure/ipam/releases/tag/v3.5.0

All resources, including the Container Registry, now have a stable identifier. Please give it a try and let me know if there are any other Bicep issues.

Thanks!