azure / aca-dotnet-workshop Goto Github PK

Please describe the feature.

Add support for Java language as well. Idea is that same architecture will be created using Java as language runtime as well and attendees can follow either of the language path based on which language team is using today.

May be in future, this leaves us scope for adding additional runtime as well

Please describe the feature.

Presently, the Backend API and Backend Processor have rights at the Service Bus level. We need to bring those down into the specific topics, so that the apps do not have universal read or write permission on the bus.

I can take care of this as I already did this for Contoso Theme Parks.

Please describe the feature.

We have scrubbed the documentation for the low-hanging Markdown Lint fruit by removing a lot of noise. Now it's time to refine the rules in .markdownlist.json and apply them to the documentation.

Check which rules should be enforced, which should be relaxed, and which one should have exceptions.

Please describe the feature.

Our documentation needs to have updated terminology for terms such as "Microsoft Entra ID" instead of "Azure Active Directory." We also need to ensure proper naming and casing. We can enforce some of that in rules in the .markdownlint.json file.

Please describe the feature.

We need to switch to Workload Profiles as that's where Azure Container Apps is moving by default. We can still use consumption within Workload Profile. We do not need to use dedicated hardware.

Please describe the feature.

@pankajagrawal16 based on our discussion here are the suggested changes to the structure for module 10:

• Modify the title of module 10 to reflect that fact that it will cover both bicep and ci/cd pipeline
• From within the bicep section inform the user that they could skip it and go directly to the CI/CD pipeline as they have the option to fork the repo and build the ci/ci pipeline without having to manually build the bicep files.
• From within the ci/cd section inform the user that they could reference the bicep section if they wanted to learn more.

Please describe the feature.

I don't yet see a good way to get started as a contributor to the documentation. Whether this is a local setup via the makefile or using a dev container, it may be helpul to have instructions.

Describe the bug

https://github.com/Azure/aca-dotnet-workshop/actions/runs/8631209186 Workflow is broken.

Need to fix in some way

Expected behavior

Should work

Actual behavior

Fails

Reproduction Steps

Merge to main and publish action fails.

Please describe the feature.

MK docs for material is much modern framework for building docs/workshop like this. It has much better support for better UX out of the box, when documenting workshops like this especially if catering alot of docs and supporting multiple language runtimes etc.

https://squidfunk.github.io/mkdocs-material/

Please describe the feature.

Steps to reproduce the current issue here:

microsoft/vscode-docker#4149

Please describe the feature.

We need a user-assigned managed identity to access Azure Container Registry in order to pull images to create Azure Container Apps. Using a system-assigned managed identity does not work because we can't create one until the container app create, but that won't exist until we can securely pull an image from the registry using an identity. Chickens and eggs, rejoice!

Please describe the feature.

The external emoji generator dependency has been deprecated and moved into mkdocs-material.

When using squidfunk/mkdocs-material:latest and running make docs-local, I presently see these messages:

Describe the bug

When running the Set-Variables.ps1 script, I get the following error:

PS C:\dev\CodeSamples\TasksTracker.ContainerApps> .\Set-Variables.ps1
At C:\dev\CodeSamples\TasksTracker.ContainerApps\Set-Variables.ps1:74 char:41

• "Write-Host "Set $i variable$($i -eq 1 ? '' : 's')."" | Out-File -F ...

•                                     ~
  

Unexpected token '?' in expression or statement.
At C:\dev\CodeSamples\TasksTracker.ContainerApps\Set-Variables.ps1:76 char:43

• Write-Host "nWrote $i variable$($i -eq 1 ? '' : 's') to $file.n"

•                                       ~
  

Unexpected token '?' in expression or statement.
+ CategoryInfo : ParserError: (:) [], ParseException
+ FullyQualifiedErrorId : UnexpectedToken

I am not particularly familiar with PowerShell, but I have tried to adjust the quotes, etc. in those commands, but to no avail. Would you mind offering me some guidance please?

Expected behavior

From the workshop instructions: "Execute the script. You will do this repeatedly throughout the modules. The output of the script will inform you how many variables are written out."

Actual behavior

As per the description:

At C:\dev\CodeSamples\TasksTracker.ContainerApps\Set-Variables.ps1:74 char:41

• "Write-Host "Set $i variable$($i -eq 1 ? '' : 's')."" | Out-File -F ...

•                                     ~
  

Unexpected token '?' in expression or statement.
At C:\dev\CodeSamples\TasksTracker.ContainerApps\Set-Variables.ps1:76 char:43

• Write-Host "nWrote $i variable$($i -eq 1 ? '' : 's') to $file.n"

•                                       ~
  

Unexpected token '?' in expression or statement.
+ CategoryInfo : ParserError: (:) [], ParseException
+ FullyQualifiedErrorId : UnexpectedToken

Reproduction Steps

Just run the script in the latest (or any I think) version of PowerShell.

We need to consider upgrading Dapr.AspNetCore NuGet to latest version 1.11. There might be some breaking changes which we need to take care of, for example. See the component type "pubsub.azure.servicebus.topics". This was not the case with Dapr version 1.9. The only supported way to consume message in Service Bus was via Topics, Dapr 1.11 now support Azure Service Bus topics and queues.

• Add an NSG to the Container App Environment subnet
• Add App Gateway instructions to shield container apps
• Remove external access to container apps
• Add UDR on Container App Environment subnet
• Add Azure Firewall for egress protection
• Add validation steps to demonstrate security improvements

Please describe the feature.

Currently the mkdocs server being run from within the docker container is serving at Serving on http://0.0.0.0:8000/. Any way that can be changes to serving on http://localhost:8000/. This way when folks click on the link it will take them to the correct url instead of asking the user to modify it in the browser.

Please describe the feature.

Upgrade workshop to make use of newer and cleaner .bicepparam file instead of json for iac.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/parameter-files?tabs=Bicep

Describe the bug

When an email address had not been entered yet, and the user attempts to load tasks, the web app crashes.

Expected behavior

The web app loads an empty Create view.

Actual behavior

The web app crashes with this error:

Reproduction Steps

1. Load the TasksTracker.WebPortal.Frontend.Ui URL. For example, [https://tasksmanager-frontend-webapp.whitewater-42989893.eastus.azurecontainerapps.io]
2. Press Load My Tasks.
3. Observe the error.

Describe the bug

The warning is complaining about a file that exists in the directory. Need to investigate the reason behind this false positive.

Expected behavior

No warning should be thrown.

Actual behavior

Warning should be thrown.

Reproduction Steps

Run the local mkdocs server by running the following command in a bash prompt (e.g. wsl on windows). Make sure you are at the root directory: make docs-local

Please describe the feature.

Each module should have a clearly defined intro, body, and outro. I noticed we are not quite clear on this.

1. Intro: Tell them what they are going to achieve.
2. Body: Show them what they are achieving.
3. Outro: Tell them what they have achieved.

Please describe the feature.

Support for IAC sample to deploy application architecture in ACA Landing Zone accelerator

https://github.com/Azure/aca-landing-zone-accelerator

Please describe the feature.

https://techcommunity.microsoft.com/t5/apps-on-azure-blog/introducing-jobs-for-azure-container-apps/ba-p/3826677

Please describe the feature.

.NET 8 will be released in November 2023. Once generally available, update our instructions appropriately.

Please describe the feature.

Having the cost associated with the workshop deployment and the tiers used in each Azure services involved in the workshop will be helpful

Please describe the feature.

Presently, we only provide guidance save and restore variables in between workshop sessions and terminals for PowerShell. Our workshop supports shell scripts as well, however, and we would like to see a pull request with a contribution.

Describe the bug

In Module 10 it should state that, if someone (like me) followed along with the whole workshop and wants to use their own sourcecode, they would need to adjust the port numbers in the parameters file according to what they have in their Dockerfiles. Otherwise, the container apps would listen on port 80 and get into timeouts.

Expected behavior

See bug description.

Actual behavior

If you don't change port numbers, the container apps will get session timeouts in cases where the Dockerfile-builds make the containers listen on different ports.

Reproduction Steps

See "Actual behavior".

Allow users to host the ACA cluster in a VNET behind an Application Gateway or Azure Front Door.

Please describe the feature.

As this workshop is extensive, it's likely that errors along the way may occur. Therefore, it would be beneficial to add git instructions to maintain a local git repo and commit after every module. In case of a module not working as intended, the workshop participant can then roll back to a last known-good state.

Please describe the feature.

Starting with .NET 8, port 8080 has become the default port (instead of port 80). We should move towards using port 8080 going forward.

As the new .NET 8 images use non-root users, port 80, which is a privileged port, needed to change to a non-privileged port to ensure non-root containers could function.