We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maven Plugin for Azure Web Apps 1.5.4
pom.xml
<!-- Java Runtime Stack for App on Linux--> <runtime> <os>linux</os> <javaVersion>jre8</javaVersion> <webContainer>tomcat 8.5</webContainer> </runtime> <deployment> <resources> <resource> <directory>${project.basedir}/target</directory> <includes> <include>*.war</include> </includes> </resource> </resources> </deployment> </configuration> </plugin>
Deploy web app in the current subscription that is set up in az account show.
Tying to deploy in the subscription at the top of az account list.
follow the Quickstart at: https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-java deployment will not be conducted in the right subscription using Cloud Shell if you have multiple subscriptions.
in plugin configuration, add:
<subscriptionId>${SUBSCRIPTIONID}</subscriptionId>
The text was updated successfully, but these errors were encountered:
#289
Sorry, something went wrong.
Fixed om #665
No branches or pull requests
Plugin name and version
Maven Plugin for Azure Web Apps 1.5.4
Plugin configuration in your
com.microsoft.azure azure-webapp-maven-plugin 1.5.4 v2 ${RESOURCEGROUP_NAME} ${WEBAPP_NAME} ${REGION}pom.xml
Expected behavior
Deploy web app in the current subscription that is set up in az account show.
Actual behavior
Tying to deploy in the subscription at the top of az account list.
Steps to reproduce the problem
follow the Quickstart at:
https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-java
deployment will not be conducted in the right subscription using Cloud Shell if you have multiple subscriptions.
Workaround
in plugin configuration, add:
The text was updated successfully, but these errors were encountered: