Now the Kladde goes to Azure. You extend the AppHost from lesson 2.9.3 with what is different in Azure, and leave the rest to the Azure Developer CLI, azd for short. azd reads the AppHost, builds the images, creates the resources from lesson 2.9.4 and ships the Kladde. At the end, you sign in on Azure, book an appointment, read the logs and delete everything again.
Set aside two hours in a row for this lesson. Costs run between azd up and azd down, and the exercise is built so that you finish
both on the same day.
azd, and why not aspire deploy
azd is a command-line tool from Microsoft that brings an application together with its infrastructure to Azure. It understands Aspire AppHosts, but also Bicep templates of your own, several environments and pipelines.
The Aspire CLI can now ship by itself, with aspire deploy, and Aspire's documentation recommends that way for new projects. The
course stays with azd: in K3, you write Bicep templates of your own, manage environments and set up a pipeline, and azd is the tool for
all of that. What you learn here about environments, resource groups and teardown applies to both ways.
Install azd and sign in:
winget install microsoft.azd
azd version
azd auth login
On macOS you install azd with brew install azure/azd/azd, on Linux with curl -fsSL https://aka.ms/install-azd.sh | bash.
azd auth login opens the browser; sign in with the account that owns the subscription from lesson 2.9.4.