Hello,
This workshop is scheduled for a May 2019 update. Please review open issues #6 #7 and #27 and give your suggested updates for SME review.
Thanks,
Dawnmarie

Is your feature request related to a problem? Please describe.
Microsoft announced that .net framework 4.8 is the last major version of .net framework. Next .net version will be .net 5, but will be based on .net core. It will be nice to have source code updated to address such announcements from Microsoft.

https://devblogs.microsoft.com/dotnet/introducing-net-5/
https://devblogs.microsoft.com/dotnet/net-core-is-the-future-of-net/

Describe the solution you'd like
.net core based application, or at least .net framework 4.8

The august-2018-testfix branch is ready for review and QC.

Folder and document names have been updated. Please check your HOL documents for links that use folder names in their path and make sure they are still valid and working.

waiting on update bit.ly for both lab links to point to correct master branch path

Exercise 2: Task 5: Setup the function
For function app console is completely changed in azure portal, please update the lab guide as per new console.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Hello,
I received a security vulnerability alert for this workshop. Please review and let me know if I can close as "risk is tolerable to this project" or if we should mark as an enhancement to be addressed in the May update. Thanks!

1 bootstrap vulnerability found in …/ContosoEvents.Web/packages.config

Remediation
Upgrade bootstrap to version 3.4.1 or later. For example:

Always verify the validity and compatibility of suggestions with your codebase.

Details
CVE-2019-8331
More information
moderate severity
Vulnerable versions: >= 3.0.0, < 3.4.1
Patched version: 3.4.1
In Bootstrap 4 before 4.3.1 and Bootstrap 3 before 3.4.1, XSS is possible in the tooltip or popover data-template attribute. For more information, see: https://blog.getbootstrap.com/2019/02/13/bootstrap-4-3-1-and-3-4-1/

@Microsoft/microsoft-cloud-workshop

Author suggested updates:
Below is a summary of what we had discussed for the update in our earlier discussions. There are also some subtleties that will be added here in terms of the way we choose to cover AKS setup, Kubernetes features like ingress and load balancing to follow a more "Kubernetes" typical approach (the lab was originally converted from a DC/OS lab which is OK but doesn't fit as naturally in the way we show load balancing setup).
 
Also with the below, I'd like to suggest we use an aspnetcore sample instead of node.js - the value of this lab is more about the platform and devops / containers - the open source story using node.js doesn't seem to be a value add and it would be nice to show how app insights integrates with aspnetcore and how to handle logging, environment overrides, secrets, etc. in aspnetcore.
 
Workshop rewrite:
• refresh the scenario and associated workshop sample
• have mongodb migrate to cosmosdb
• have full ci/cd discussion for containers and environment promotion
• include secret management
• include autoscale and load balancing features
 
Lab rewrite:
• update for new sample - refresh the scenario / idea a little
• add vsts / ci / cd workflows with azure container registry
• add cosmosdb work, add back end to sample, show local dev/test and prod migration
• add secrets
• add autoscale of nodes + container scale (if possible, AKS may not be positioned to do this yet)
• add app insights for end to end tracing and visibility
• update use of kubernetes load balancing and ingress features

SME suggested updates:
Visual Studio connected environment - to Azure Dev Space
http://landinghub.visualstudio.com/devspaces
CLI Tool allows to work in backend

Mongo DB to Cosmos DB
https://blogs.msdn.microsoft.com/alimaz/2018/04/21/migrating-mongodb-databases-from-mongo-lab-to-cosmos-db/
Put in references (WDS) may be too time consuming for lab
ASPC net core app - starter code with mongo backend (dockerized)
Lift and shift that to the cloud
Mongo to Cosmos - modernize the DB - move away from the cluster
Talking point - functions, options, and reasoning

Biggest customer ask - I'd like to deploy AKS using custom vnet on Azure
Possible good in Customer needs section
https://docs.microsoft.com/en-us/azure/aks/networking-overview?WT.mc_id=linkedin

• Item to do #2

Azure updated CosmosDB collection. It is mandatory to give partition value which was not necessary earlier.

In prep and on diagram Azure Functions are under a separate RG but in steps it's being provisioned under same RG as other components (Which should be fine).

Exercise 3
Task 5 (Item 24) - Instead of copy and paste can we publish the binary (ideally using beta v2 Functions)

Task 6 - Need to mention we need to configure App Insight or switch to classic view for logs as per Guide.

Exercise 4
Task 1 (Item 8) We need to update StoreLocation and StoreName in Cloud.xml PublishProfile

Please submit septemeber update

WDS PPT image, slide 17 (preferred solution) does not pass the color contrast test for accessibility standards.

In the HOL, Exercise 1, Tasks 2, 4-7 (infra edition) or 2-6 (developer edition) can be easily accomplished with deploying a predefined Azure Resource Manager template, which would save attendees time and allow them to focus on the more substantive parts of the workshop.

WDS powerpoint abstract does not completely match Readme. Content is the same, wording is different. I recommend leaving it.

Sample issue for linking

Hi Team,

I did go through the docs and found that you have provided a link to source code on Dropbox. It would be great if you can commit it here though.

Thank you

HOL to Hands on Lab
WDS to Whiteboard design session
Create updated HTML files once folders are correctly named

Abstracts for the HOL step-by-step and unguided, both Infrastructure and Developer editions (four documents in total) are incorrect. They use the WDS abstracts and not the HOL abstracts. The correct abstract appears later but in the incorrect spot.

In the Related References, can we update the links for Technology choices, DevOps checklist and Architecture styles to point to public URL instead of internal links?

• Technology choices https://docs.microsoft.com/en-us/azure/architecture/guide/technology-choices/compute-overview
• DevOps checklist https://docs.microsoft.com/en-us/azure/architecture/checklist/dev-ops
• Architecture styles https://docs.microsoft.com/en-us/azure/architecture/guide/architecture-styles/

@givenscj
Hi Chris,

I've merged the November test/fix with the master and will update the HTML files next. There are two potential security vulnerabilities flagging this workshop. Please review and respond as needed.

https://github.com/Microsoft/MCW-Microservices-architecture/network/alerts

There is also open issue #22 that was probably addressed during your test/fix. Please review the issue and respond/close as appropriate.

Thanks.