[Example] Function App on Consumption Plan with Custom Domain and App Serivce Managed Certificate

[miqm]

Bicep Example usage of creating Azure Function App with Custom Domain and Managed Certificate.

This requires module usage, as we need to modify Microsoft.Web/sites/hostNameBindings twice - first time to add the custom domain (which is required for certificate generation), second - to assign the generated certificate.

[ghost]

All CLA requirements met.

[miqm]

The tests are failing because there's a property password missing, however it's not required when enabling manged certificate - it's required only when uploading custom one.

Even in the ARM quickstarts - https://github.com/Azure/azure-quickstart-templates/blob/master/201-web-app-custom-domain-and-ssl/azuredeploy.json password property is not provided.

[miqm]

@alex-frankel How we can merge this example? do we need to wait for some warning suppression mechanism first?

[alex-frankel]

apologies for missing this one - I think you need to do a few things to get the test to pass:

• pull the latest from main
• use the any() function (doc) to get rid of the warning:

resource functionAppCustomHostCertificate 'Microsoft.Web/certificates@2020-06-01' = {
  name: '${applicationName}.${dnsZone}'
  location: location
  dependsOn: [
    functionAppCustomHost
  ]
  properties: any({
    serverFarmId: hostingPlan.id
    canonicalName: '${applicationName}.${dnsZone}'
  })
}

• add a blank line to the end of the .bicep files

[miqm]

Thanks @alex-frankel , I thought about the any function, but I didn't thought about putting all properties in it. I updated the PR.

[alex-frankel]

great! I do now see there is a conflict in the examples.ts - can you get that resolved and then we can merge

[anthony-c-martin]

FWIW looks like the fix to swagger for the non-required password field is being tracked by Azure/azure-rest-api-specs#5029

[miqm]

Conflict resolved. We probably would need some build-time task to generate that file to avoid such conflicts...

Regarding the password field, seems it's not likely for it to be out in swagger anytime soon...