Try container apps with various workloads

• .NET core 3.1 based Dapr applications
• .NET 6.0 / Functions v4 applications

hence .devcontainer is configured to do a primary .NET Core 3.1 SDK and a secondary .NET 6.0 SDK install

sign in with Azure CLI

az login --use-device-code

switch to the desired subscription

az account set -s "{subscription-name-or-id}"

re-register Microsoft.Web

az provider register --namespace Microsoft.Web

sign in with Pulumi

pulumi login

• change ca-pulumi-dotnet/Program.cs to FunctionAppStack.cs.
• deploy

cd ca-pulumi-dotnet pulumi stack init dev pulumi up

• go to load testing resource in Azure Portal
• create test
• upload ca-pulumi-dotnet/loadtest.jmx
• in parameters set ingress_url to loadtestfapp1 output value
• Create the test

Result:

deploy sample

cd app1 dotnet publish cd .. cd app2 dotnet publish cd .. cd ca-dotnet pulumi up

test sample

pulumi stack select dev curl $(pulumi stack output urlapp2)/health curl $(pulumi stack output urlapp1)/health curl -v $(pulumi stack output urlapp1)/healthapp2

the first 2 test individual health endpoints, and the 3rd tests service invocation from app1 to app2

for the jump VM, a SSH public key needs to be provided before Pulumi deployment

pulumi config set sshpubkey "ssh-rsa AA...FY" 

• VNET integration

• Container Apps Quickstart
• VSCode devcontainer setup
• other vscode-dev-containers features