Azure deployment can be hard.<\/p>\n
To deploy and maintain azure resources, we are using bicep templates (a main template, invoking child modules to create individual resources). In addition we have environment-parameter-files, to encapsulate the differences between each environment.<\/p>\n
Today, I had to add some Function App Alerts via the bicep-template. Basically the only part in this task, was to create a new module, that could create the Alerts for an array of Function Apps.<\/p>\n
Feeling confident, I made the change, pushed it to the Azure Devops repository and invoked the Devops pipeline.<\/p>\n
Sadly it failed with this very non-descriptive failure<\/p>\n
I had no idea about the reason – since i had changed nothing wrt. keyvaults and added no references.<\/p>\n The ARM-template file that Devops was trying to deploy, was not available (we use MS agents)<\/p>\n Trying local deployment:<\/p>\n showed the same error – but gave no indications to the cause.<\/p>\n Doing a bicep build ( After hours of debugging, the error turned out to be simple: I had not given the module a name.<\/p>\n Currently, I have no idea, how this oversight could lead to the error above.<\/p>\n","protected":false},"excerpt":{"rendered":" Azure deployment can be hard. To deploy and maintain azure resources, we are using bicep templates (a main template, invoking child modules to create individual resources). In addition we have environment-parameter-files, to encapsulate the differences between each environment. Today, I had to add some Function App Alerts via the bicep-template. Basically the only part in … Continue reading “Azure Bicep deployment – non-descript error”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[30],"class_list":["post-1184","post","type-post","status-publish","format-standard","hentry","category-guides","tag-azure"],"_links":{"self":[{"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/posts\/1184","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1184"}],"version-history":[{"count":5,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/posts\/1184\/revisions"}],"predecessor-version":[{"id":1196,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=\/wp\/v2\/posts\/1184\/revisions\/1196"}],"wp:attachment":[{"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1184"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1184"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wp.bizoir.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}ERROR: InvalidTemplate - Deployment template validation failed: 'The
\ntemplate resource 'xxKeyVault' at line '1' and column '9939' is
\nnot valid: The template function 'reference' is not expected at this
\nlocation. Please see https:\/\/aka.ms\/arm-functions for usage details..
\nPlease see https:\/\/aka.ms\/arm-functions for usage details.'.<\/code><\/p>\naz bicep lint<\/code> showed no issues.<\/p>\naz deployment group what-if --name Test --resource-group rg-test-dev
\n--template-file modules\\main.bicep --parameters params\\dev.json
\n--subscription \"Test - DEV\" --mode Incremental<\/code><\/p>\naz bicep build --file modules\\main.bicep<\/code>) produced a template-file, but it was clearly not identical to the one that Devops pipeline did<\/p>\n
\nmodule functionAppAlerts 'functionAppAlerts.bicep' = {
\n name: 'functionAppAlerts'<\/strong>
\n params: {
\n actionGroupId: actionGroups.outputs.actionGroupsId
\n timerTriggeredFunctionApps: functionAppNames_timerTriggered
\n location: location
\n tags: tags
\n }
\n}<\/code><\/p>\n