Skip to content

Commit b07f1c1

Browse files
committed
update contents
1 parent de0db28 commit b07f1c1

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

asset-manager/WORKSHOP.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
> [!IMPORTANT]
44
> `GitHub Copilot app modernization for Java on Azure` is in preview and is subject to change before becoming generally available.
55
6-
`GitHub Copilot app modernization for Java on Azure` assists with app assessment, planning and code remediation. It automates repetitive tasks, boosting developer confidence and speeding up the Azure migration and ongoing optimization.
6+
`GitHub Copilot app modernization for Java on Azure` (also referred to as App Modernization for Java on Azure) assists with app assessment, planning and code remediation. It automates repetitive tasks, boosting developer confidence and speeding up the Azure migration and ongoing optimization.
77

88
In this workshop, you learn how to use `GitHub Copilot app modernization for Java on Azure` to assess and migrate a sample Java application `asset-manager` to Azure. For more information about the sample application, see [Asset Manager](README.md).
99

@@ -35,11 +35,12 @@ The following sections guide you through the process of migrating the sample Jav
3535
The first step is to assess the sample Java application `asset-manager`. The assessment provides insights into the application's readiness for migration to Azure.
3636

3737
1. Open the VS code with all the prerequisites installed on the asset manager by changing the directory to the `asset manager` directory and running `code .` in that directory.
38-
1. Open the extension `GitHub Copilot app modernization for Java on Azure`.
38+
1. Open the extension `App Modernization for Java on Azure`.
3939
1. The **Assess** button looks a triangle pointing right. Select **Assess**, the Github Copilot chat window will be opened and propose to run Modernization Assessor. Please confirm the tool usage by clicking **Continue**.
4040

41-
> **NOTE**: If you are asked to allow the tool access the language models provided by GitHub Copilot Chat, slect **Allow** to proceed.
41+
> **NOTE**: If you are asked to allow the tool access the language models provided by GitHub Copilot Chat, select **Allow** to proceed.
4242
43+
1. After each step, please manually input a response to confirm and proceed.
4344
1. Wait for the assessment to be completed and the report to be generated.
4445
1. Review the **Summary** report. Select **Propose Solution** to view the proposed solutions for the issues identified in the summary report.
4546
1. For this workshop, deselect all solutions and select **Use Azure Database for PostgreSQL** in the Solution report, then select **Confirm Solution**.
@@ -49,22 +50,24 @@ The first step is to assess the sample Java application `asset-manager`. The ass
4950

5051
1. After clicking the Migrate button in the Solution Report, Copilot chat window will be opened with Agent Mode.
5152
1. In Copilot chat window, click **Continue** repeatedly to confirm each tool action. The Copilot Agent uses various tools to facilitate application modernization. Each tool's usage requires confirmation by clicking the `Continue` button.
52-
1. Review the proposed code changes and click **Keep** to apply them.
53+
1. After each step, please manually input a response to confirm and proceed.
5354
1. Click **Continue** to confirm to run **Java Application Build-Fix** tool. This tool will attempt to resolve any build errors, in up to 10 iterations.
5455
1. After the Build-Fix tool begins, click **Continue** to proceed and show progress and migration summary.
56+
1. Review the proposed code changes and click **Keep** to apply them.
5557

5658
### Migrate to Azure Blob Storage and Azure Service Bus using Custom Formula
5759

5860
Recall that the sample Java application `asset-manager` uses AWS S3 for image storage and Spring AMQP RabbitMQ for message queuing. The `workshop` branch has additional commits that have already migrated the code for **Web Application** with custom code remediation to use Azure Blob Storage and Azure Service Bus, respectively.
5961

6062
Now, you migrate the **Worker Service** to use Azure Blob Storage and Azure Service Bus as well, by using custom formula created from existing commits that migrated the **Web Application**.
6163

62-
1. Open the sidebar of `GitHub Copilot app modernization for Java on Azure`. Hover the mouse over the **Formulas** section. Select **Create formula from source control**. This icon looks like two circles with arrows pointing to the other circle. Type **migrate web** to search for the commits that migrated the **Web Application**, and you should see two commits listed:
64+
1. Open the sidebar of `App Modernization for Java on Azure`. Hover the mouse over the **Formulas** section. Select **Create formula from source control**. This icon looks like two circles with arrows pointing to the other circle. Type **migrate web** to search for the commits that migrated the **Web Application**, and you should see two commits listed:
6365
* migrate web rabbitmq to azure service bus
6466
* migrate web s3 to azure blob storage
6567
1. Select these two commits. Click **Create New** to create a new custom formula.
6668
1. Formula name, formula description, and code location patterns will be generated in order. Press `Enter` repeatedly to confirm.
67-
1. Select and run the custom formula you created in the FORMULAS section of the sidebar of `GitHub Copilot app modernization for Java on Azure`. Follow the same steps as the predefined formula to review and apply the changes, and run the **Java Application Build-Fix** tool to apply build fixes.
69+
1. Select and run the custom formula you created in the FORMULAS section of the sidebar of `App Modernization for Java on Azure`. Follow the same steps as the predefined formula to review and apply the changes, and run the **Java Application Build-Fix** tool to apply build fixes.
70+
1. Review the proposed code changes and click **Keep** to apply them.
6871

6972
## Deploy to Azure
7073

0 commit comments

Comments
 (0)