Quickstart: Set up Spring Cloud Config Server for Azure Spring Apps
Note
The Basic, Standard, and Enterprise plans will be deprecated starting from mid-March, 2025, with a 3 year retirement period. We recommend transitioning to Azure Container Apps. For more information, see the Azure Spring Apps retirement announcement.
The Standard consumption and dedicated plan will be deprecated starting September 30, 2024, with a complete shutdown after six months. We recommend transitioning to Azure Container Apps.
Config Server is a centralized configuration service for distributed systems. It uses a pluggable repository layer that currently supports local storage, Git, and Subversion. In this quickstart, you set up the Config Server to get data from a Git repository.
Prerequisites
- JDK 17
- An Azure subscription. If you don't have a subscription, create a Trial before you begin.
- Optionally, Azure CLI version 2.45.0 or higher. Install the Azure Spring Apps extension with the following command:
az extension add --upgrade --name spring
- Optionally, the Azure Toolkit for IntelliJ.
Config Server procedures
The following procedure sets up the Config Server using the Azure portal to deploy the PetClinic sample.
Go to the service Overview page and select Config Server.
In the Default repository section, set URI to
https://github.com/azure-samples/spring-petclinic-microservices-config
.Select Validate. Validation checks the schema and accessibility of your git repo to make sure it's correct.
When validation is complete, select Apply to save your changes.
Updating the configuration can take a few minutes. You should get a notification when the configuration is complete.