You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your branch is up to date with 'origin/workshop'.
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: asset-manager/WORKSHOP.md
Signed-off-by: Ed Burns <[email protected]>
Copy file name to clipboardExpand all lines: asset-manager/WORKSHOP.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,14 +33,16 @@ Reference the doc **Getting Started.docx** for how to use the Java Migration Cop
33
33
34
34
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.
35
35
36
-
1. Open Java Migration Copilot tool in VSCode. It consists of Assessment and Prompts features currently.
37
-
1. Select **Assess**, wait for the assessment to complete, and review the assessment report.
36
+
1. Ensure Docker Desktop is running.
37
+
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 Java Migration Copilot tool in VSCode. It consists of Assessment and Prompts features currently. As of 2025-04-03, the icon looks like the M365 a copilot icon in one color.
39
+
1. The **Assess** button looks a triangle pointing right. Select **Assess**, wait for the assessment to complete, and review the assessment report.
38
40
39
41
> **NOTE**: If you are asked to allow the tool access the language models provided by GitHub Copilot Chat, slect **Allow** to proceed.
40
42
41
43
1. Select **Propose Solution** to view the proposed solutions for the issues identified in the assessment report, for example, **Migrate from AWS S3 to Azure Blob Storage**, **Migrate from Spring AMQP RabbitMQ to Azure Service Bus** and **Use Azure Database for PostgreSQL**.
42
44
1. For this workshop, deselect all solutions and select **Use Azure Database for PostgreSQL**, then select **Confirm the Solution**.
43
-
1. Review the solution details and select **Migrate** to initiate the migration process.
45
+
1. Review the solution details and select **Migrate** to initiate the migration process.**Migrate** is located in the middle pane.
44
46
45
47
### Migrate to Azure Database for PostgreSQL Flexible Server using Predefined Prompt
46
48
@@ -58,7 +60,7 @@ Once you complete this step, suggest opening **Source Control** view to revisit
58
60
59
61
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.
60
62
61
-
Now, you migrate the **Worker Service** to use Azure Blob Storage and Azure Service Bus as well, by using custom propmt created from existing commits that migrated the **Web Application**.
63
+
Now, you migrate the **Worker Service** to use Azure Blob Storage and Azure Service Bus as well, by using custom prompt created from existing commits that migrated the **Web Application**.
62
64
63
65
1. Select **Create prompt from source control**, type **migrate web** to search for the commits that migrated the **Web Application**, and you should see two commits listed:
0 commit comments