azuredevcollege / trainingdays Goto Github PK

Hi,

on day4 in Commit the changes to your local branch you point out that you can use the VSCode extension Azure repos. However, this has been deprecated and is therefore no longer available in the VSCode Marketplace and is no longer actively developed. I think you should change or remove this reference.

More Info

Thanks,
René

As discussed in our meeting we want to integrate GitHub Workflows in day4.
The goal is, as with Azure Pipelines, to create a staged deployment to the following environments:

• Development
• Testing

In the pull request, all necessary components are built to avoid build breaks. After a merge into the main branch, the development environment is directly deployed. After a manual check, the test environment is deployed.

2. Cloud Shell Add Data to Cosmos Integrate Node JS APP
3. Change Feed
4. Ende - Links zu Docs
5. Verweis auf Code Samples

-size parameter seems not to work as expected.

without a date the policy wont work. You may want to reflect this in the description

It is the last challenge of the day. Give an overview of deployment strategy (environment etc), remove azuredevcollege condition in Actions workflows and deploy common components to Azure.

The ARM Template for the initial deployment in Challenges 10 and 11 does not work anymore. It deploys the vms just fine but fails to install the DSC extension. This is due to the fact that the attributes "modulesUrl" and "webZipURI" still point to the root folder of the challenge although the required files were moved to "challengeXX/scripts".

I've already fixed this in a local branch but cannot push it, as I don't have permissions.

'day1/challenges/Challenge2/TemplateDeployment.PNG'
'day1/challenges/Challenge2/TemplateDeployment.png'
'day1/challenges/Challenge2/TemplateDeployment2.PNG'
'day1/challenges/Challenge2/TemplateDeployment2.png'
'day1/challenges/Challenge2/TemplateDeployment3.PNG'
'day1/challenges/Challenge2/TemplateDeployment3.png'
'day1/challenges/Challenge3/enableBackup1.PNG'

The sample application is deployed to dev and a test environment after a PullRequest is merged. The deployment to test environment must be manually approved.

Deployment failed:

{
"status": "Failed",
"error": {
"code": "InvalidResourceReference",
"message": "Resource /subscriptions/a2ba2440-3367-4053-86aa-07bcecc57e6f/resourceGroups/rg-vnetpeering/providers/Microsoft.Network/virtualNetworks/VNET1/subnets/VMSubnet1 referenced by resource /subscriptions/a2ba2440-3367-4053-86aa-07bcecc57e6f/resourceGroups/rg-vnetpeering/providers/Microsoft.Network/networkInterfaces/VMonVNET1-nic1 was not found. Please make sure that the referenced resource exists, and that both resources are in the same region.",
"details": []
}
}

We need a new section in the corresponding setup challenges of Day 2 / 7 for participants to be able to setup the Azure environment upfront:

• What permissions are needed to complete all challenges?
• How to test if a user has the correct setup?

CC: @AndreasM009

Linux-based WebApps and Functions can now be mixed with Windows-based resources. We can get rid of the "TUX" RGs.

Publisher, subscriber and queue consumer use topic and subscription name hard coded:

• SCM Indexer Function
• SCM Image Resizer
• SCM VisitReport
• SCM TextAnalytics

We need to change the names in Challenges of day3.

Maybe it is a simple API that is hosted with Azure AppService

These are not needed for day 5 (AFAIK) and will make the checkpoint deployment much easier.

CC: @waeltken

Add condition to all workflows so they only run within the azuredevcollege organisation

• delete face api - bonus challenge
• delete computer vision - bonus challenge
• review rest for correct spelling/logic

e.g.

• Import the Azure Dev College's training repository to your org
• Create your first Pull Request
• Deploy the sample application to your subscription

Add a bonus challenge operate the static website (backed by an Azure Storage Account - Static Website) with a Content Delivery Network

Terraform 0.14 has been released. Check, if everything works as expected with that version.

To protect the main branch. Changes can only be added within a pull request.

inform the users when clicking the deployment button to hit the right subscription.
->idea - an animated gif might help

• Intro to Azure Search with indexes, schema, scoring, indexer
• Create Search service
• demo search features

the Service Bus Entity between SCM Resources API and Image Resizer Function is the Queue named thumbnails instead of a Topic named Image Resizer, i guess?

Use failOnStdErr: true in all workflows as the AzureCLI writes some lines to stderr.

We should switch to the portal view instead of using the Kubernetes Dashboard...and maybe mention a few alternatives like Lens, Octant, k9s etc. that the participants can use.

Implicit flow is not recommended anymore.

Compared to the other challenges, in the bonus challenge it could be better described, which files to edit and how to apply the changes. Nevertheless, with some help, I managed to find the right files and deploy the changes 👍

Create workflows for Day5.

As example you can compare your ARM Template with the following code snippet:
Remove the IPAddress parameter
retake some screenshots as the flow is misleading - wont enter an ip address in an arm template.

We should do a rework of day 3 based on the feedback from participants:

• focus more on CosmosDB + Cognitive Services (? - TBD: we have a dedicated day for it in the AI DevCollege)
• TBD: skip CosmosDB challenges at all and just do demos? Make the challenges optional?
• remove Azure Data Factory: push data to CosmosDB via code or prepare files for uploading to a db
• show how to use different APIs of CosmosDB (SQL + MongoDB + Gremlin - maybe let participants decide which one to test-drive?)
• TBD: add demo for CAP/PACELC theorem?
• TBD: multi-master demo? Important to understand the impact on RTO/RPO
• show CosmosDB change feed. TBD: only in talk + optional challenge?
• remove or at least reduce challenge for Azure SQL DB (probably all participants have already dealt with SQL)
• TBD: reduce content for Azure Search to the minimum (e.g. make indexing documents an optional challenge and just mention the option in the talk?)

CC: @CodeUnicornMartha, @alschroe, @AndreasM009

Prepare day4 (GitHub) project structure for apps and challenges.

Error from server (BadRequest): error when creating "local-secrets.yaml": Secret in version "v1" cannot be handled as a Secret: v1.Secret.Data: decode base64: illegal base64 data at input byte 192, error found in #10 byte of ...|xMeklxVT0","CONTACTS|...

es scheinen in der mit replace_variables.sh erzeugten Datei ein = zu fehlen am Ende der Strings:
CONTACTSLISTENCONNSTR
CONTACTSSENDCONNSTR
TAENDPOINT
TAKEY

When your FW at home blocks simple IP browsing.