You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: Code=InvalidTemplate; Message=Deployment template validation failed: 'The template reference 'identities1Res' is not valid: could not find template resource or resource copy with this name. Please see https://aka.ms/arm-function-reference for usage details.'.
Note that if you remove the two module references and leave the output which has the same value as the input for the modules the error does not appear which is strange.
@slavizh was this template deploying with Bicep v0.30 and then broke with v0.31? The compiled template seems to be the same across both Bicep versions, so I'm wondering if this was caused by a backend change:
@jeskew This particular template I have not tested with the previous release as I have build the template in order to reproduce the issue and provide a simpler easier way to test it. Overall the original that this is based on I am pretty sure it was working at some point as I have tested many different scenarios. For sure there is some bug if it acts differently if you input the same code to module and if the same code is only in output.
Bicep version
Bicep CLI version 0.31.34 (ec82b47)
Describe the bug
I get error:
Error: Code=InvalidTemplate; Message=Deployment template validation failed: 'The template reference 'identities1Res' is not valid: could not find template resource or resource copy with this name. Please see https://aka.ms/arm-function-reference for usage details.'.
in some specific scenario.
This is related to #13674
To Reproduce
To reproduce:
test1.bicep
Note that if you remove the two module references and leave the output which has the same value as the input for the modules the error does not appear which is strange.
bicepconfig used
Template works fine if extensibility is not enabled.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: