Adding breadcrumb footers

00-setup-your-environment/README.md

@@ -95,3 +95,7 @@ This training lab requires the following to be installed on your machine:
 The environment variable `JAVA_HOME` should be set to the path of `javac` in the JDK installation.
 
 You can then use Visual Studio Code or an IDE of your choice.
+
+---
+
+➡️ Next Section: [Migrate a Spring Cloud Application](../01-migrate-spring-cloud-application/README.md)

01-migrate-spring-cloud-application/README.md

@@ -1,4 +1,4 @@
-# Migrate a Spring Cloud App
+# Migrate a Spring Cloud Application
 
 In this section, we're going to take a pre-existing Spring Cloud application, consisting of four microservices, and migrate it to Azure Spring Cloud in its entirety.
 
@@ -10,12 +10,12 @@ For expediency, let's create the Azure Spring Cloud instance from Azure CLI.
 
 First, you will need to come up with a name for your Azure Spring Cloud instance.
 
--__The name must be unique among all Azure Spring Cloud Instances across all of Azure__. Consider using your username as part of the name.
+- __The name must be unique among all Azure Spring Cloud Instances across all of Azure__. Consider using your username as part of the name.
 - The name can contain only lowercase letters, numbers and hyphens. The first character must be a letter. The last character must be a letter or number. The value must be between 4 and 32 characters long.
 
 To save minimize, set the variable `RESOURCE_GROUP_NAME` to the name of the resource group created in the previous section. Set the variable `SPRING_CLOUD_NAME` to the name of the Azure Spring Cloud instance to be created:
 
->🛑Be sure to substitute your own values for `RESOURCE_GROUP_NAME` and `SPRING_CLOUD_NAME` as described above.
+>🛑Be sure to substitute your own values for `RESOURCE_GROUP_NAME` and `SPRING_CLOUD_NAME` as described above. __`SPRING_CLOUD_NAME` must be globally unique.__
 
 ```bash
 RESOURCE_GROUP_NAME=spring-cloud-lab
@@ -196,4 +196,10 @@ Once all apps have the status `Running`, click on the Gateway app. In the PiggyM
 
 You should see the front page of the PiggyMetrics app. Click "Create new account", and once you've created an account, play around with the application for a couple of minutes to generate some log and traffic data. Then, proceed to the next section.
 
-![PiggyMetrics front page](media/03-piggymetrics-front-page.png)
+![PiggyMetrics front page](media/03-piggymetrics-front-page.png)
+
+---
+
+⬅️ Previous section: [00 - Set Up Your Environment](../00-setup-your-environment/README.md)
+
+➡️ Next section: [02 - Troubleshooting](../02-troubleshooting/README.md)

02-troubleshooting/README.md

@@ -29,3 +29,9 @@ AppPlatformLogsforSpring
 ```
 
 ![Query logs](media/01-logs-query.png)
+
+---
+
+⬅️ Previous section: [01 - Migrate a Spring Cloud Application](../00-setup-your-environment/README.md)
+
+➡️ Next section: [03 - Observability and Scaling](../03-observability-and-scaling/README.md)

03-observability-and-scaling/README.md

@@ -41,3 +41,9 @@ Here, we can scale the microservice up by increasing its allotment of CPU and RA
 Return to the "Apps" page under the Azure Spring Cloud Instance. You should now see the Instance count increased to 3. The status of the service may change to "Upgrading" once the new replicas come up, but should return to running, once all the instances are available.
 
 ![instance-count-after-scaling](media/05-instance-count-after-scaling.png)
+
+---
+
+⬅️ Previous section: [02 - Troubleshooting](../02-troubleshooting/README.md)
+
+➡️ Next section: [04 - Enable Continuous Deployment](../04-enable-continuous-deployment/README.md)

04-enable-continuous-deployment/README.md

@@ -125,3 +125,9 @@ AppPlatformLogsforSpring
 1. To make builds faster and more reliable, [Azure Artifacts Feeds can be configured](https://docs.microsoft.com/en-us/azure/devops/artifacts/maven/upstream-sources?view=azure-devops) to cache 3rd party dependencies instead of fetching them from Maven Central with every build.
 
 1. The Deployment task we implemented with Azure CLI can be reused by adding parametrizing some of the command arguments, such as the resource group name, the Azure Spring Cloud instance name, and the Jar file name. Then, right-click on the task and click "Create Task Group". This will prevent the duplication of the script across multiple microservice pipelines.
+
+---
+
+⬅️ Previous section: [03 - Observability and Scaling](../03-observability-and-scaling/README.md)
+
+➡️ Next section: [05 - Enable Blue-Green Deployment](../05-enable-blue-green-deployment/README.md)

05-enable-blue-green-deployment/README.md

@@ -135,3 +135,7 @@ Watch the second stage of the pipeline run. Once it completes, navigate to the p
 ![Change deployed to production](media/08-change-deployed-to-production.png)
 
 __Note:__ the prior deployment does not automatically get deleted. It's still available (and still consuming resources), should you need to revert at a moment's notice. We may wish to subsequently add another delayed stage to our pipeline that deletes the old deployment after some delay.
+
+---
+
+⬅️ Previous section: [04 - Enable Continuous Deployment](../04-enable-continuous-deployment/README.md)