Deploying a Spring Boot app to Azure

Open a terminal window.

Create a local directory to hold your Spring Boot application by typing mkdir SpringBoot

Change to that directory by typing cd SpringBoot.

Clone the Spring Boot Getting Started sample project into the directory you created by typing git clone https://github.com/spring-guides/gs-spring-boot

Change to the directory of the completed project by typing cd gs-spring-boot/complete

Build the JAR file using Maven by typing ./mvnw clean package

When the web app has been created, start it by typing ./mvnw spring-boot:run

Test it locally by either visiting http://localhost:8080 or typing curl http://localhost:8080 from another terminal window.

You should see the following message displayed: Greetings from Spring Boot!

Before started, you will need to provision an Azure Spring Apps cluster for instance using Azure Portal.

From the terminal window, config your web app with Maven Plugin for Azure Spring Apps by typing ./mvnw com.microsoft.azure:azure-spring-cloud-maven-plugin:1.3.0:config. This maven goal will first authenticate with Azure, if you have logged in with Azure CLI, it will consume its existing authentication token. Otherwise, it will get you logged in with azure-maven-plugin automatically.

Then you can configure the deployment, run the maven command in the Command Prompt and select the Azure Spring Apps cluster you just created, accept default for app name, then press 'y' to expose public access for this app. When you get the Confirm (Y/N) prompt, press 'y' and the configuration is done.

[email protected]:~/gs-spring-boot/complete$ mvn com.microsoft.azure:azure-spring-cloud-maven-plugin:1.3.0:config
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------< com.example:spring-boot >-----------------------
[INFO] Building spring-boot 0.0.1-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- azure-spring-cloud-maven-plugin:1.3.0:config (default-cli) @ spring-boot ---
[INFO] [Correlation ID: xxx] Instance discovery was successful
Available Azure Spring Apps Services:
 1. xxx*
Select Azure Spring Apps for deployment: [1-28] (1): 1
[INFO] Using service: xxx
Input the app name (spring-boot):
Expose public access for this app spring-boot? (y/N):y
Summary of properties:
Subscription id   : xxx
Service name      : xxx
App name          : spring-boot
Public access     : true
Instance count    : 1
CPU count         : 1
Memory size(GB)   : 1
Runtime Java version : Java 8
Confirm to save all the above configurations (Y/n):

Optionally, open your pom.xml to see all the configuration written.

<plugin>
    <groupId>com.microsoft.azure</groupId>
    <artifactId>azure-spring-cloud-maven-plugin</artifactId>
    <version>1.3.0</version>
    <configuration>
        <subscriptionId>xxx</subscriptionId>
        <clusterName>xxx</clusterName>
        <appName>spring-boot</appName>
        <isPublic>true</isPublic>
        <deployment>
            <cpu>1</cpu>
            <memoryInGB>1</memoryInGB>
            <instanceCount>1</instanceCount>
            <runtimeVersion>Java 8</runtimeVersion>
            <resources>
                <resource>
                    <filtering/>
                    <mergeId/>
                    <targetPath/>
                    <directory>${project.basedir}/target</directory>
                    <includes>
                        <include>*.jar</include>
                    </includes>
                </resource>
            </resources>
        </deployment>
    </configuration>
</plugin>

Once you have configured all of the settings in the preceding sections, you are ready to deploy your web app to Azure Spring Apps with mvn azure-spring-cloud:deploy. Maven will deploy your web app to Azure. It might take a few minutes before the web app is accessible at the URL shown in the output. Navigate to the URL in a Web browser. You should see the message displayed: Greetings from Spring Boot! Note that this simple Spring Boot sample app is not using any Spring Cloud components like Discovery Client, thus registration status will be down while the app is up and running normally.