bicep VS azure-cli-extensions

I just created my first Emacs package, a major mode for the Bicep Language. I have to say it was quite easy to get to this. The Emacs docs are great and using LSP made it easy to add completion.

My requirements need me to populate APIM's set-backend-service and rewrite-uri. With the above json, a user-defined function is required. And alas, as of now it's not possible in bicep :(

Bicep unfortunately chose to create a DSL instead of just exposing the dotnet API to allow IaC. Now there is a nuget package for Bicep core (https://github.com/Azure/bicep/pull/5826) you may be able to use dotnet code.

Yes, as of version 0.3 Azure Bicep is production ready. It is supported by Microsoft Support Plans and Bicep has 100% parity with what can be accomplished by ARM template.

I suggest reading the bicep documentation as I don't think it will require 12,000 words to determine the answers to your questions.

Bicep is open source with a strong community supporting it. All the binaries for the different supported operating systems can be downloaded from the official releases page of the Bicep open source project.

It sounds like you're running into this: https://github.com/Azure/bicep/issues/1631

The backend code is C#, with CosmosDb/TableStorage for persistence. Our client tools are also mostly C#, with some TypeScript, and some Python. Our backend code is currently closed-source, but our Bicep repo gives an example of our coding style.

The Microsoft Azure Deployments team aims to make deploying resources to Azure simple, safe, predictable, and reliable. We own the Template deployment orchestration service, client-facing tools including our open source DSL - Bicep, and various other services aimed at bringing customers up to speed with Infrastructure as Code. We are at the heart of the Azure control plane with great opportunities for cross-team collaboration and impact, have a lot of autonomy to shape the direction of our own products, and enjoy having a hands-on approach with customers to help drive our feature design.

u/nezoic can you open an issue for this here please: https://github.com/Azure/bicep/issues

Azure CLI

With a bit of research I was able to find a very simple solution for this problem, and Azure CLI was again my best friend.

To learn more about Azure CLI, check this documentation.

Azure CLI installed and connected to your subscription

4) All the next steps that we're about to do can be done with the UI in Azure Portal, but we will use Azure CLI as much as possible. Also, I will name my Resource Group and App Service Plan as MyResourceGroup and MyLinuxPlan respectively. If you already have a Resource Group and App Service plan, you can continue using them. Or you can follow next step and substitute with names of your own choosing.

Bicep comes with a CLI that you can install locally on Windows, MacOS, and Linux. That gives you the ability to build and deploy your Bicep files with Azure CLI.

Azure CLI

The first two options that come to mind are Azure CLI and Azure PowerShell. Both allow to create resources using commands, so we could write a shell or PowerShell script to automate things.

Now we need to configure our SWA function app and add our function keys and URLs. You can get the function key for each function app running the following commands on the Azure CLI :