tye VS azure-cli-extensions

System.CommandLine is the official .NET library that provides common functionality for command-line applications. This includes features like argument parsing, automatic help text generation, tab autocomplete, suggestions, corrections, sub-commands, user cancellation, and much more. Many official .NET tools are built on top of System.CommandLine, including the .NET CLI, Kiota, Tye, numerous Azure tools, and other .NET additional tools.

I though tye was a typo but it is an actual project: https://github.com/dotnet/tye

I would like to build modules, either in a modular monolith style, or in a microservice style using DAPR and/or Tye.

GitHub: https://github.com/dotnet/tye

If you like working with docker compose, you might want to take a look at https://github.com/dotnet/tye

I think it's a good option or docker compose with your services only. Maybe check out project tye. Although it seems abandoned.

Thoughts on scaffold vs Tye ?

https://github.com/dotnet/tye for starting up many services/projects and tying them all together

Docker, and check out also Tye https://github.com/dotnet/tye

NOTE: If you're really curious to know what the --enable-network-observability flag does in Azure CLI, you can read through the source code here

The portal is handy, but we won’t use it in this article. Instead, let’s install the Azure command-line interface. The most recent version at the moment of writing is 2.30.0.

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