How to Deploy Spring Boot applications from Azure CLI

Article
09/30/2024

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. For more information, see Migrate Azure Spring Apps Standard consumption and dedicated plan to Azure Container Apps.

This article applies to: ✅ Java ❎ C#

This article applies to: ✅ Basic/Standard ❎️ Enterprise

Azure Spring Apps enables Spring Boot applications on Azure.

You can launch applications directly from Java source code or from a pre-built JAR. This article explains the deployment procedures.

Prerequisites

Before you begin, ensure that your Azure subscription has the required dependencies:

Tip

The Azure Cloud Shell is a free interactive shell that you can use to run the steps in this article. It has common Azure tools preinstalled, including the latest versions of Git, JDK, Maven, and the Azure CLI. If you are logged in to your Azure subscription, launch your Azure Cloud Shell from shell.azure.com. You can learn more about Azure Cloud Shell by reading our documentation

Install the Azure CLI extension

Install the Azure Spring Apps extension for the Azure CLI with the following command

az extension add --name spring

Provision a service instance using the Azure CLI

az login
az account list -o table
az account set --subscription <subscription-id>

Create a resource group to contain your service in Azure Spring Apps. You can learn more about Azure Resource Groups.

az group create --location eastus --name <resource-group-name>

Run the following commands to provision an instance of Azure Spring Apps. Prepare a name for your service in Azure Spring Apps. The name must be between 4 and 32 characters and can contain only lowercase letters, numbers, and hyphens. The first character of the service name must be a letter and the last character must be either a letter or a number.

az spring create --resource-group <resource-group-name> --name <resource-name>

The service instance will take about five minutes to deploy.

Set your default resource group name and Azure Spring Apps instance name using the following commands:

az config set defaults.group=<service-group-name>
az config set defaults.spring=<service-instance-name>

Create the application in Azure Spring Apps

The following command creates an application in Azure Spring Apps in your subscription. This creates an empty service to which you can upload your application.

az spring app create --name <app-name>

Deploy your Spring Boot application

You can deploy your application from a pre-built JAR or from a Gradle or Maven repository. Find instructions for each case below.

Deploy a pre-built JAR

To deploy from a JAR built on your local machine, ensure that your build produces a fat-JAR.

To deploy the fat-JAR to an active deployment

az spring app deploy --name <app-name> --artifact-path <path-to-fat-JAR>

To deploy the fat-JAR to a specific deployment

az spring app deployment create --app <app-name> \
    --name <deployment-name> \
    --artifact-path <path-to-fat-JAR>

Deploy from source code

Azure Spring Apps uses kpack to build your project. You can use Azure CLI to upload your source code, build your project using kpack, and deploy it to the target application.

Warning

The project must produce only one JAR file with a main-class entry in the MANIFEST.MF in target (for Maven deployments) or build/libs (for Gradle deployments). Multiple JAR files with main-class entries will cause the deployment to fail.

For single module Maven / Gradle projects:

cd <path-to-maven-or-gradle-source-root>
az spring app deploy --name <app-name> --source-path

For Maven / Gradle projects with multiple modules, repeat for each module:

cd <path-to-maven-or-gradle-source-root>
az spring app deploy --name <app-name> --source-path \
    --target-module <relative-path-to-module>

Show deployment logs

Review the kpack build logs using the following command:

az spring app show-deploy-log --name <app-name>

Note

The kpack logs will only show the latest deployment if that deployment was built from source using kpack.

Assign a public endpoint to an application

Open the Apps pane to view apps for your service instance.
Select an application to view its Overview page.
Select Assign endpoint to assign a public endpoint to the application. This process can take a few minutes.
Copy the URL from the Overview page and paste it into your browser to view running application.

Next steps

Quickstart: Monitoring Azure Spring Apps with logs, metrics, and tracing

More samples are available on GitHub: Azure Spring Apps Samples.

Share via