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
Bicep version
run bicep --version via the Bicep CLI, az bicep version via the AZ CLI or via VS code by navigating to the extensions tab and searching for Bicep
0.26.170
(also tried with 0.28.10, no difference)
ResourceTypeNotSupported: The resource type '/' does not support diagnostic settings.
We have updated recently to define the resource names in a user-defined function called namingPatternGenerator. Prior to this change, the deployment of the diagnostic setting worked perfectly. I have also amended to directly apply the expected logic app standard name as a string passed to stdLAppName, which would reverse any deploy-time nondeterminacy which might be the cause - this made no difference.
To Reproduce
Deploy a main.bicep containing these modules using azd provision
Additional context
The error message given is wrong, as we didn't specify a resource type of '/'. Whatever the error actually is, Bicep should say so.
I've checked https://github.com/Azure/bicep/issues/12959 where the author remarks that they can't prove that an arbitrary string is a resource identifier - I don't believe this is the case here as the diagnostic settings module uses:
Hi @TWolversonReply, this issue has been marked as stale because it was labeled as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. Thanks for contributing to bicep! 😄 🦾
Bicep version
run
bicep --version
via the Bicep CLI,az bicep version
via the AZ CLI or via VS code by navigating to the extensions tab and searching for Bicep0.26.170
(also tried with 0.28.10, no difference)
Describe the bug
Given the relevant template modules:
Deploying with azd returns an error message:
ResourceTypeNotSupported: The resource type '/' does not support diagnostic settings.
We have updated recently to define the resource names in a user-defined function called
namingPatternGenerator
. Prior to this change, the deployment of the diagnostic setting worked perfectly. I have also amended to directly apply the expected logic app standard name as a string passed tostdLAppName
, which would reverse any deploy-time nondeterminacy which might be the cause - this made no difference.To Reproduce
Deploy a main.bicep containing these modules using
azd provision
Additional context
The error message given is wrong, as we didn't specify a resource type of '/'. Whatever the error actually is, Bicep should say so.
I've checked
https://github.com/Azure/bicep/issues/12959
where the author remarks that they can't prove that an arbitrary string is a resource identifier - I don't believe this is the case here as the diagnostic settings module uses:This can be proved a valid resource identifier, and it is being passed a string I know refers to a Logic App that exists.
The text was updated successfully, but these errors were encountered: