Skip to content

Commit 99d3e2e

Browse files
committed
validation
1 parent 3fabed9 commit 99d3e2e

File tree

6 files changed

+7
-21
lines changed

6 files changed

+7
-21
lines changed

articles/app-service/deploy-github-actions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ If you use prefer the Azure CLI to deploy to App Service, you can use the GitHub
268268
```
269269

270270
More information on the GitHub Action for CLI and how to use and configure it can be found in the [Azure CLI GitHub action](https://github.com/Azure/cli).
271-
More information on the az webapp deploy command, how to use and the parameter details can be found in the [az webapp deploy documentation](/cli/azure/webapp?view=azure-cli-latest#az-webapp-deploy).
271+
More information on the az webapp deploy command, how to use and the parameter details can be found in the [az webapp deploy documentation](/cli/azure/webapp#az-webapp-deploy).
272272

273273
### How do I deploy a startup file?
274274

91.3 KB
Loading
107 KB
Loading
77.7 KB
Loading

articles/app-service/tutorial-java-jboss-mysql-app.md

Lines changed: 6 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ First, you set up a sample data-driven app as a starting point. For your conveni
9494
:::column span="2":::
9595
**Step 3:** In the codespace terminal:
9696
1. Run `mvn clean wildfly:run`.
97-
1. When you see the notification `Your application running on port 8080 is available.`, select **Open in Browser**.
97+
1. When you see the notification `Your application running on port 8080 is available.`, wait a few seconds longer for the WildFly server to finish loading the application. Then, select **Open in Browser**.
9898
You should see the sample application in a new browser tab.
9999
To stop the WildFly server, type `Ctrl`+`C`.
100100
:::column-end:::
@@ -147,30 +147,16 @@ Sign in to the [Azure portal](https://portal.azure.com/) and follow these steps
147147
1. *Linux Plan*: **Create new** and use the name **msdocs-jboss-mysql**.
148148
1. *Pricing plan*: **Premium V3 P0V3**. When you're ready, you can [scale up](manage-scale-up.md) to a different pricing tier.
149149
1. *Deploy with your app*: Select **Database**. Azure Database for MySQL - Flexible Servier is selected for you by default. It's a fully managed MySQL database as a service on Azure, compatible with the latest community editions.
150-
1. Select **Next: Deployment**.
151-
1. After validation completes, select **Create**.
152-
:::column-end:::
153-
:::column:::
154-
:::image type="content" source="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-2.png" alt-text="A screenshot showing how to configure a new app and database in the Web App wizard." lightbox="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-2.png":::
155-
:::column-end:::
156-
:::row-end:::
157-
:::row:::
158-
:::column span="2":::
159-
**Step 3:** In the **Deployment** tab, fill out the form as follows.
160-
1. *Continuous deployment*: **Enable**.
161-
1. *Oranization*: Select your GitHub alias.
162-
1. *Repository*: **msdocs-jboss-mysql-sample-app**.
163-
1. *Branch*: **main**.
164150
1. Select **Review + create**.
165151
1. After validation completes, select **Create**.
166152
:::column-end:::
167153
:::column:::
168-
:::image type="content" source="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-3.png" alt-text="A screenshot showing how to configure Deployment tab in the Web App wizard." lightbox="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-3.png":::
154+
:::image type="content" source="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-2.png" alt-text="A screenshot showing how to configure a new app and database in the Web App wizard." lightbox="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-2.png":::
169155
:::column-end:::
170156
:::row-end:::
171157
:::row:::
172158
:::column span="2":::
173-
**Step 4:** The deployment takes a few minutes to complete. Once deployment completes, select the **Go to resource** button. You're taken directly to the App Service app, but the following resources are created:
159+
**Step 3:** The deployment takes a few minutes to complete. Once deployment completes, select the **Go to resource** button. You're taken directly to the App Service app, but the following resources are created:
174160
- **Resource group**: The container for all the created resources.
175161
- **App Service plan**: Defines the compute resources for App Service. A Linux plan in the *Basic* tier is created.
176162
- **App Service**: Represents your app and runs in the App Service plan.
@@ -180,7 +166,7 @@ Sign in to the [Azure portal](https://portal.azure.com/) and follow these steps
180166
<!-- Author note: Azure Database for MySQL's networking is not the same as other databases. It integrates with a private DNS zone, not with a private endpoint. -->
181167
:::column-end:::
182168
:::column:::
183-
:::image type="content" source="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-4.png" alt-text="A screenshot showing the deployment process completed." lightbox="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-4.png":::
169+
:::image type="content" source="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-3.png" alt-text="A screenshot showing the deployment process completed." lightbox="./media/tutorial-java-jboss-mysql-app/azure-portal-create-app-mysql-3.png":::
184170
:::column-end:::
185171
:::row-end:::
186172

@@ -339,7 +325,7 @@ Like the JBoss convention, if you want to deploy to the root context of JBoss, n
339325
**Step 4 (Option 1: with GitHub Copilot):**
340326
1. Start a new chat session by clicking the **Chat** view, then clicking **+**.
341327
1. Ask, "*@workspace How does the app connect to the database?*" Copilot might give you some explanation about the `java:jboss/MySQLDS` data source and how it's configured.
342-
1. Ask, "*@workspace I want to replace the data source defined in persistence.xml with an existing JNDI data source in JBoss but I want to do it dynamically.*". Copilot might give you a code suggestion similar to the one in the **Option 2: without GitHub Copilot** steps below and even tell you to make the change in the class.
328+
1. Say, "*The data source in JBoss in Azure will use the JNDI name java:jboss/env/jdbc/AZURE_MYSQL_CONNECTIONSTRING_DS.*" Copilot might give you a code suggestion similar to the one in the **Option 2: without GitHub Copilot** steps below and even tell you to make the change in the class.
343329
GitHub Copilot doesn't give you the same response every time, you might need to ask more questions to fine-tune its response. For tips, see [What can I do with GitHub Copilot in my codespace?](#what-can-i-do-with-github-copilot-in-my-codespace).
344330
:::column-end:::
345331
:::column:::
@@ -440,7 +426,7 @@ When you're finished, you can delete all of the resources from your Azure subscr
440426
:::row:::
441427
:::column span="2":::
442428
**Step 1:** In the search bar at the top of the Azure portal:
443-
1. Enter the resource group name.
429+
1. Enter the resource group name *msdocs-jboss-mysql_group*.
444430
1. Select the resource group.
445431
:::column-end:::
446432
:::column:::

0 commit comments

Comments
 (0)