Alexander Sehr

We use the same approach leveraged by @brwilkinson in our [CARML modules](https://github.com/Azure/ResourceModules/blob/main/arm/Microsoft.Storage/storageAccounts/.parameters/parameters.json) for e.g. RBAC ```json (...) "queueServices": { "value": { "queues": [ { "name": "queue1", "metadata": {}, "roleAssignments": [...

> > Thinking about it more, another option which avoids the size expansion issue you mentioned would be to just have a file with exported variables: > > > >...

> sumption is the `import` statement, not via a `module` - this actually does dead code elimination, so should avoid bloating the template. Here's what my examp As they say...

> ```bicep > @export() > @description('Push artifacts to or pull artifacts from a container registry.') > var AcrPush = '8311e382-0749-4cb8-b61a-304f252e45ec' > > @export() > @description('Can manage service and the APIs')...

> Please open a support ticket so this can be routed and we will have someone reach out internally Hey @stephaniezyen & @alex-frankel, we're seeing this issue across all resource...

> If it's happening across several different resource types, then it may be some more generic to ARM or the Deployment Service. Can you provide some recent correlation IDs and...

> or the diagnosticDependencies to get the storageAccountNa Hey @miqm, thank you for your reply. However, there is no dependency in the 2 deployments you mentioned. The `nestedDependencies` & `diagnosticDependencies`...

Hey @miqm, I can certainly try. Given the issue that it doesn't happen on every run (as the timing sometimes happens to check out) I hope it won't take to...

> @AlexanderSehr can you make a test and instead deploying the test module as a for-loop deploy 2 regular modules or just one and see if then it will be...

All modules converted