Update for spring boot externalized configuration

openshift-labs · Jun 21, 2021 · 0d39a1e · 0d39a1e
1 parent efbdf82
commit 0d39a1e
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 4 deletions.
diff --git a/assets/middleware/rhoar-microservices/greeting-service-mini.png b/assets/middleware/rhoar-microservices/greeting-service-mini.png
diff --git a/middleware/middleware-spring-boot/microservices-1/02-deploy-to-openshift.md b/middleware/middleware-spring-boot/microservices-1/02-deploy-to-openshift.md
@@ -32,9 +32,11 @@ Run the following command to deploy the application to OpenShift:
 
 There's a lot that happens here so lets break it down:
 
-For the deployment to OpenShift we are using the [JKube](https://www.eclipse.org/jkube/) tool through the [`openshift-maven-plugin`](https://www.eclipse.org/jkube/docs/openshift-maven-plugin), which is configured in our ``pom.xml``{{open}} (found in the `<profiles/>` section).
+For the deployment to OpenShift we are using the [JKube](https://www.eclipse.org/jkube/) tool through the [`openshift-maven-plugin`](https://www.eclipse.org/jkube/docs/openshift-maven-plugin), which is configured in our ``pom.xml``{{open}} (found in the `<profiles/>` section). The deployment may take a few minutes to complete.
 
-Now that our application is deployed, navigate to our route in the OpenShift Web View or click [here](http://spring-boot-configmap-greeting-dev.[[HOST_SUBDOMAIN]]-80-[[KATACODA_HOST]].environments.katacoda.com/). We should see the following screen, meaning everything was successful:
+You can run the command ``oc rollout status -w dc/spring-boot-configmap-greeting``{{execute}} to watch and wait for the deployment to complete.
+
+Once the application deployment completes, navigate to our route in the OpenShift Web View or click [here](http://spring-boot-configmap-greeting-dev.[[HOST_SUBDOMAIN]]-80-[[KATACODA_HOST]].environments.katacoda.com/). We should see the following screen, meaning everything was successful:
 
 ![Greeting Service](/openshift/assets/middleware/rhoar-microservices/greeting-service-mini.png)
 

diff --git a/middleware/middleware-spring-boot/microservices-1/03-modify-the-configmap.md b/middleware/middleware-spring-boot/microservices-1/03-modify-the-configmap.md
@@ -23,7 +23,7 @@ Change the `greeting.message` property to: `greeting.message=Bonjour, you picked
 
 ![Greeting Service](/openshift/assets/middleware/rhoar-microservices/editconfigmap.png)
 
-Hit `Save` and that's all there is to it!
+Hit `Save` (at the bottom of the editor) and that's all there is to it!
 
 **3. Test changes**
 
@@ -36,4 +36,4 @@ This means that we were able to modify our application behavior through External
 
 ## Congratulations
 
-You have now learned how to handle Externalized Configuration with ConfigMaps through OpenShift. By creating a configmap, we're able to modify application properties on the fly and simply rollout the new changes to our application.
+You have now learned how to handle Externalized Configuration with ConfigMaps through OpenShift. By creating a `ConfigMap`, we're able to modify application properties on the fly and simply rollout the new changes to our application.