bicep VS azure-cli

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

Isn't Azure CLI written in Python?

Even though it seems like a pretty good little hack – this is not supported. The Portal would also bug out and refuse to display Environments correctly if the resource were created with “Other” workflow:

Similar issue and troubleshooting here. https://github.com/Azure/azure-cli/issues/13855

Oh ya, I caught that. This is where I found the command to run: https://github.com/Azure/azure-cli/issues/9501#issuecomment-610979930

I'm following the below doc to patch in some redirect URIs for a script that creates an App in Azure. https://github.com/Azure/azure-cli/issues/9501

Yes, as a 10-year user of Tumbleweed, generally OpenSUSE is left behind when it comes to downloading binary packages from first-party sources.

Even for the Microsoft software that "supports" OpenSUSE, historically that support was by expecting OpenSUSE users to use their RHEL packages which didn't always work well. [1] [2] (I don't know if the problems are still there, because I switched to the Docker image for `az` and stopped using `powershell`)

[1]: https://github.com/PowerShell/PowerShell/issues/6184

[2]: https://github.com/Azure/azure-cli/issues/7523

What about Az CLI? The proof of concept is easy, but it isn't a top priority for Azure team 😥, just check GitHub. The gist is the only thing I've found, but I'm not using it.

I always feel like Azure gives you like 95% of a solution to your problem, but is always missing a critical feature or usability nicety you'd really like. For example, I've been working with Azure Key Vault. I'd like to list what's in my Key Vault. Great, I thought, I'll use az keyvault certificate list. Turns out that only returns the first 25 results AND there's no way to list more without using the API directly... I had to write my own tool to solve that and a couple other usability issues.