spring-cloud-azure-starter-appconfiguration-config-entraid-sample

page_type	sample
languages	java
products	azure-app-configuration
name	Refreshing Configuration Properties From App Configuration in Spring Boot Application using Entra ID
description	This sample demonstrates how to refresh configuration properties from App Configuration in Spring Boot application using Entra ID.

Refreshing Configuration Properties From App Configuration in Spring Boot Application

Prerequisite

• A Java Development Kit (JDK), version 8.
• Apache Maven, version 3.0 or later.

How to run

Setup your App Configuration Store

1. To create your Azure App Configuration store, you can use:

   az appconfig create --resource-group <your-resource-group> --name <name-of-your-new-store> --sku Standard
   

2. Create the test key in your new store:

   az appconfig kv set --key /application/config.message --value testKey --name <name-of-your-new-store> --yes
   

3. Create the feature flag in your new store:

   az appconfig feature set --feature alpha --name <name-of-your-new-store>
   

4. Create monitor trigger.

   az appconfig kv set --key sentinel --value 1 --name <name-of-your-new-store> --yes
   

This value should match the spring.cloud.azure.appconfiguration.stores[0].monitoring.triggers[0].key value in bootstrap.properties.

Setup your environment

1. Set an environment variable named APP_CONFIGURATION_ENDPOINT, and set it to the endpoint to your App Configuration store. At the command line, run the following command and restart the command prompt to allow the change to take effect:

   setx APP_CONFIGURATION_ENDPOINT "endpoint-of-your-app-configuration-store"

   If you use Windows PowerShell, run the following command:

   $Env:APP_CONFIGURATION_ENDPOINT = "endpoint-of-your-app-configuration-store"
   

   If you use macOS or Linux, run the following command:

   export APP_CONFIGURATION_ENDPOINT='endpoint-of-your-app-configuration-store'

Run the application

1. Build the application

   mvn clean package

2. Run the application

   mvn spring-boot:run

3. Go to localhost:8080 which will display the value testKey.

4. Update key to new value.

   az appconfig kv set --key /application/config.message --value updatedTestKey --name <name-of-your-new-store> --yes
   

5. Update monitor trigger, to trigger refresh.

   az appconfig kv set --key sentinel --value 2 --name <name-of-your-new-store> --yes
   

6. Refresh page, this will trigger the refresh update.

7. After a couple seconds refresh again, this time the new value updatedTestKey will show.

8. Go to localhost:8080/feature-flag/alpha which will display the status of the feature flag.

9. Update the feature flag in your App Configuration store.

   az appconfig feature enable --feature alpha --name <name-of-your-new-store>
   

10. Refresh page, this will trigger the refresh update.

11. After a couple seconds refresh again, this time the new value updatedTestKey will show.

12. Go to localhost:8080/feature-flag/alpha which will display the status of the feature flag.

13. Update the feature flag in your App Configuration store.

    az appconfig feature enable --feature alpha --name <name-of-your-new-store>
    

14. After a couple seconds refresh the page twice, this time the feature flag status will show as enabled.

Deploy to Azure Spring Apps

Now that you have the Spring Boot application running locally, it's time to move it to production. Azure Spring Apps makes it easy to deploy Spring Boot applications to Azure without any code changes. The service manages the infrastructure of Spring applications so developers can focus on their code. Azure Spring Apps provides lifecycle management using comprehensive monitoring and diagnostics, configuration management, service discovery, CI/CD integration, blue-green deployments, and more. To deploy your application to Azure Spring Apps, see Deploy your first application to Azure Spring Apps.