We have a deployment running in an azure devops server and base currently on az cli, now we want to go for bicep. I created bicep definitions for the resources what works easily. But now I got stuck when I try to deploy the azure function resource into that new resources. All ducumentation I found ends also at this point. The function I want to deploy is developed in .Net 6 and is currently deployed via ZipDeployment.

At this point I ask myself whether bicep is perhaps not intended to transport the binaries into the resources. Instead, it is only intended to generate the resources and from this point on we are better off using our existing azure cli scripts.

I found the possibility to use Microsoft.Web/sites/extensions@2021-02-01 with a packageUri but therefore the binaries need to be available online. So I would need to upload them first to a blob what is also not that simple in bicep and the way I found looks like an workaround including some security issues.

Is there someone who does this in pure bicep? If so, what is the best way to get the bianries deployed? Or is bicep only used to create the resources and the binaries are deployed into the resource in another way?

1 Answer 1

  1. Bicep to create function app and define its configuration
  2. To deploy, you may use Azure DevOps pipelines with Deploy Azure Function App task: AzureFunctionApp@2 - Azure Functions Deploy v2 task

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.