reorder lab sections (#55)

## Purpose reorder the sections of the doc ## Does this introduce a breaking change?  ``` [ ] Yes [x] No ``` ## Pull Request Type What kind of change does this Pull Request introduce?  ``` [ ] Bugfix [ ] Feature [ ] Code style update (formatting, local variables) [ ] Refactoring (no functional changes, no api changes) [x] Documentation content changes [ ] Other... Please describe: ```
Azure-Samples · Sep 25, 2024 · cff9669 · cff9669
1 parent 0da2665
commit cff9669
Show file tree

Hide file tree

Showing 21 changed files with 63 additions and 17 deletions.
diff --git a/docs/05_lab_openai/01.md → docs/05_lab_openai/0501.md b/docs/05_lab_openai/01.md → docs/05_lab_openai/0501.md
diff --git a/docs/05_lab_openai/02.md → docs/05_lab_openai/0502.md b/docs/05_lab_openai/02.md → docs/05_lab_openai/0502.md
diff --git a/docs/05_lab_openai/openlab_openai_aca.md → docs/05_lab_openai/05_openlab_openai_aca.md b/docs/05_lab_openai/openlab_openai_aca.md → docs/05_lab_openai/05_openlab_openai_aca.md
@@ -5,7 +5,7 @@ nav_order: 7
 has_children: true
 ---
 
-# Lab 05: Integrate with Azure OpenAI.
+# Lab 5: Integrate with Azure OpenAI
 
 # Student manual
 

diff --git a/docs/08_lab_azd/0801.md → docs/06_lab_automation/0601.md b/docs/08_lab_azd/0801.md → docs/06_lab_automation/0601.md
diff --git a/docs/08_lab_azd/0802.md → docs/06_lab_automation/0602.md b/docs/08_lab_azd/0802.md → docs/06_lab_automation/0602.md
diff --git a/.../08_lab_azd/08_openlab_azd_deployments.md → ...6_lab_automation/06_openlab_automation.md b/.../08_lab_azd/08_openlab_azd_deployments.md → ...6_lab_automation/06_openlab_automation.md
@@ -1,36 +1,41 @@
 ---
-title: 'Lab 8: Use Azd to deploy the lab solution'
+title: 'Lab 6: Automatically deploy lab solution to Azure Container Apps'
 layout: default
-nav_order: 10
+nav_order: 8
 has_children: true
 ---
 
-# Lab 7: Use Azd to deploy the lab solution to Azure Container App
+# Lab 6: Automatically deploy lab solution to Azure Container Apps
 
 # Student manual
 
 ## Lab scenario
 
-Use [azd](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/) tool to deploy the petclinic solution to Azure Container Apps environment.
+In the Lab 2, Lab 3, Lab 4 and Lab 5 we deploy the petclinic microservice solution to Azure Container Apps step by step.
+These steps are full of details but time costing.
+
+In this lab, we import a new tool [azd](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/) to help deploy the solution to Azure with single command.
 
 ## Objectives
 
 After you complete this lab, you will be able to:
 
-- Deploy the sample solution to new ACA environment.
-- Test your setup
+- Get familiar with the azd tool.
+- Deploy the petclinic solution to new ACA environment.
+- Test your setup.
 
 ## Lab Duration
 
-- **Estimated Time**: 60 minutes
+- **Estimated Time**: 90 minutes
 
 ## Instructions
 
 During this lab, you will:
 
-- Update the configuration according to you azure environment
+- Prepare your azd tools environment.
+- Get your Azure Registry ready and fill the configuration files.
 - Run `azd up` command to deploy the sample soluton to Azure Container Apps.
-- Test your setup
+- Test your setup.
 
 ## Limits
 

diff --git a/docs/06_lab_security/0601.md → docs/07_lab_security/0701.md b/docs/06_lab_security/0601.md → docs/07_lab_security/0701.md
diff --git a/docs/06_lab_security/0602.md → docs/07_lab_security/0702.md b/docs/06_lab_security/0602.md → docs/07_lab_security/0702.md
diff --git a/docs/06_lab_security/0603.md → docs/07_lab_security/0703.md b/docs/06_lab_security/0603.md → docs/07_lab_security/0703.md
diff --git a/docs/06_lab_security/0604.md → docs/07_lab_security/0704.md b/docs/06_lab_security/0604.md → docs/07_lab_security/0704.md
diff --git a/docs/06_lab_security/0605.md → docs/07_lab_security/0705.md b/docs/06_lab_security/0605.md → docs/07_lab_security/0705.md
diff --git a/docs/06_lab_security/0606.md → docs/07_lab_security/0706.md b/docs/06_lab_security/0606.md → docs/07_lab_security/0706.md
diff --git a/docs/06_lab_security/0607.md → docs/07_lab_security/0707.md b/docs/06_lab_security/0607.md → docs/07_lab_security/0707.md
diff --git a/docs/06_lab_security/0608.md → docs/07_lab_security/0708.md b/docs/06_lab_security/0608.md → docs/07_lab_security/0708.md
diff --git a/...6_lab_security/06_openlab_security_aca.md → ...7_lab_security/07_openlab_security_aca.md b/...6_lab_security/06_openlab_security_aca.md → ...7_lab_security/07_openlab_security_aca.md
@@ -1,11 +1,11 @@
 ---
-title: 'Lab 6: Protect endpoints using Web Application Firewalls'
+title: 'Lab 7: Protect endpoints using Web Application Firewalls'
 layout: default
-nav_order: 8
+nav_order: 9
 has_children: true
 ---
 
-# Lab 05: Protect endpoints using Web Application Firewall
+# Lab 7: Protect endpoints using Web Application Firewall
 
 # Student manual
 

diff --git a/...ivate/07_openlab_private_endpoints_aca.md → ...ivate/07_openlab_private_endpoints_aca.md b/...ivate/07_openlab_private_endpoints_aca.md → ...ivate/07_openlab_private_endpoints_aca.md
@@ -1,11 +1,11 @@
 ---
-title: 'Lab 7: Secure MySQL database and Key Vault using a Private Endpoint'
+title: 'Lab 8: Secure MySQL database and Key Vault using a Private Endpoint'
 layout: default
-nav_order: 9
+nav_order: 10
 has_children: true
 ---
 
-# Lab 06: Secure MySQL database and Key Vault using a Private Endpoint
+# Lab 8: Secure MySQL database and Key Vault using a Private Endpoint
 
 # Student manual
 
@@ -39,4 +39,3 @@ During this lab, you will:
 
 {: .note }
 > The instructions provided in this exercise assume that you successfully completed the previous exercise and are using the same lab environment, including your Git Bash session with the relevant environment variables already set.
-
diff --git a/docs/07_lab_private/0701.md → docs/08_lab_private/0801.md b/docs/07_lab_private/0701.md → docs/08_lab_private/0801.md
diff --git a/docs/07_lab_private/0702.md → docs/08_lab_private/0802.md b/docs/07_lab_private/0702.md → docs/08_lab_private/0802.md
diff --git a/docs/07_lab_private/0703.md → docs/08_lab_private/0803.md b/docs/07_lab_private/0703.md → docs/08_lab_private/0803.md
diff --git a/docs/07_lab_private/0704.md → docs/08_lab_private/0804.md b/docs/07_lab_private/0704.md → docs/08_lab_private/0804.md
diff --git a/docs/08_lab_private/08_openlab_private_endpoints_aca.md b/docs/08_lab_private/08_openlab_private_endpoints_aca.md
@@ -0,0 +1,42 @@
+---
+title: 'Lab 7: Secure MySQL database and Key Vault using a Private Endpoint'
+layout: default
+nav_order: 10
+has_children: true
+---
+
+# Lab 06: Secure MySQL database and Key Vault using a Private Endpoint
+
+# Student manual
+
+## Lab scenario
+
+You now have your application deployed into a virtual network and the microservices connection requests from the internet must pass through your Application Gateway instance with Web Application Firewall enabled. However, the apps communicate with the backend services, such Azure Database for MySQL Flexible Server and Key Vault via their public endpoints. In this exercise, you will lock them down by implementing a configuration in which they only accept connections that originate from within your virtual network.
+
+## Objectives
+
+After you complete this lab, you will be able to:
+
+- Lock down the Azure Database for MySQL Flexible Server instance by redeploying it in a subnet
+- Lock down the Key Vault instance by using a private endpoint
+- Test your setup
+
+The below image illustrates the end state you will be building in this lab.
+
+![lab 8 overview](../../images/acalab6.png)
+
+## Lab Duration
+
+- **Estimated Time**: 60 minutes
+
+## Instructions
+
+During this lab, you will:
+
+- Lock down the Azure Database for MySQL Flexible Server instance by redeploying it in a subnet
+- Lock down the Key Vault instance by using a private endpoint
+- Test your setup
+
+{: .note }
+> The instructions provided in this exercise assume that you successfully completed the previous exercise and are using the same lab environment, including your Git Bash session with the relevant environment variables already set.
+