Merge pull request #296254 from dingmeng-xue/migration-aca-review

Add migration tooling and update blue-green deployment

Author: v-shils

articles/spring-apps/includes/deprecation-note.md

@@ -3,10 +3,10 @@ author: KarlErickson
 ms.author: karler
 ms.service: azure-spring-apps
 ms.topic: include
-ms.date: 09/30/2024
+ms.date: 03/17/2025
 ---
 
 > [!NOTE]
-> The **Basic**, **Standard**, and **Enterprise** plans will be deprecated starting from mid-March, 2025, with a 3 year retirement period. We recommend transitioning to Azure Container Apps. For more information, see the [Azure Spring Apps retirement announcement](../basic-standard/retirement-announcement.md).
+> The **Basic**, **Standard**, and **Enterprise** plans entered a retirement period on March 17, 2025. For more information, see the [Azure Spring Apps retirement announcement](../basic-standard/retirement-announcement.md).
 >
-> The **Standard consumption and dedicated** plan will be deprecated starting September 30, 2024, with a complete shutdown after six months. We recommend transitioning to Azure Container Apps. For more information, see [Migrate Azure Spring Apps Standard consumption and dedicated plan to Azure Container Apps](../consumption-dedicated/overview-migration.md).
+> The **Standard consumption and dedicated** plan entered a retirement period on September 30, 2024, with a complete shutdown by the end of March 2025. For more information, see [Migrate Azure Spring Apps Standard consumption and dedicated plan to Azure Container Apps](../consumption-dedicated/overview-migration.md).

articles/spring-apps/migration/migrate-to-azure-container-apps-blue-green.md

@@ -1,23 +1,19 @@
 ---
-title: The Experience of Blue-Green Deployment in Azure Container Apps
-description: Describes the experience of blue-green deployment in Azure Container Apps.
+title: Blue-Green Deployment to Azure Container Apps
+description: Describes blue-green deployment to Azure Container Apps.
 author: KarlErickson
 ms.author: karler
-ms.reviewer: dixue
+ms.reviewer: dingmeng-xue
 ms.service: azure-spring-apps
 ms.topic: upgrade-and-migration-article
-ms.date: 01/29/2025
+ms.date: 03/17/2025
 ms.custom: devx-track-java, devx-track-extended-java
 ---
 
-# The experience of blue-green deployment in Azure Container Apps
-
-[!INCLUDE [deprecation-note](../includes/deprecation-note.md)]
+# Blue-green deployment to Azure Container Apps
 
 **This article applies to:** ✅ Basic/Standard ✅ Enterprise
 
-This article describes blue-green deployment with Azure Container Apps.
-
 In Azure Container Apps, you can enable blue-green deployment by combining [container apps revisions](../../container-apps/revisions.md), [traffic weights](../../container-apps/traffic-splitting.md), and [revision labels](../../container-apps/revisions.md#labels).
 
 ## Create or update a container app with multiple active revisions enabled
@@ -26,11 +22,11 @@ To create a new container app with multiple active revisions enabled, use the fo
 
 ```azurecli
 az containerapp create \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
-    --environment <APP_ENVIRONMENT_NAME> \
-    --image mcr.microsoft.com/k8se/samples/test-app:<BLUE_COMMIT_ID> \
-    --revision-suffix <BLUE_SUFFIX> \
+    --resource-group <resource-group> \
+    --name <app-name> \
+    --environment <app-environment-name> \
+    --image mcr.microsoft.com/k8se/samples/test-app:<blue-commit-ID> \
+    --revision-suffix <blue-suffix> \
     --ingress external \
     --target-port 80 \
     --revisions-mode multiple
@@ -40,8 +36,8 @@ Alternatively, you can use the following command to update an existing app to en
 
 ```azurecli
 az containerapp revision set-mode \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
+    --resource-group <resource-group> \
+    --name <app-name> \
     --mode multiple
 ```
 
@@ -51,29 +47,31 @@ To deploy a new revision, use the following command:
 
 ```azurecli
 az containerapp update \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
+    --resource-group <resource-group> \
+    --name <app-name> \
     --image mcr.microsoft.com/k8se/samples/test-app:<GREEN_COMMIT_ID> \
     --revision-suffix <GREEN_SUFFIX>
 ```
 
-You can add labels to specific revisions as shown in the following example:
+To add labels to a specific revision, use the following commands:
 
 ```azurecli
 az containerapp revision label add \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
+    --resource-group <resource-group> \
+    --name <app-name> \
     --label blue \
-    --revision <APP_NAME>--<BLUE_SUFFIX>
+    --revision <blue-revision-name>
 
 az containerapp revision label add \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
+    --resource-group <resource-group> \
+    --name <app-name> \
     --label green \
-    --revision <APP_NAME>--<GREEN_SUFFIX>
+    --revision <green-revision-name>
 ```
 
-Initially, the revision with the *blue* `commitId` takes 100% of production traffic, while the newly deployed revision with the *green* `commitId` doesn't take any production traffic.
+Here, `<blue-revision-name>` is `<app-name>--<blue-suffix>`, and `<green-revision-name>` is `<app-name>--<green-suffix>`. You can only assign a label to one revision at a time.
+
+Initially, the revision with the blue `commitId` takes 100% of production traffic, while the newly deployed revision with the green `commitId` doesn't take any production traffic.
 
 In Azure Spring Apps, you can deploy at most two revisions of one app: one set as Production and the other as Staging. However, Azure Container Apps supports deploying multiple revisions for a single app.
 
@@ -83,35 +81,35 @@ Each revision in Azure Container Apps has its own URL, enabling you to test and
 
 ```azurecli
 export GREEN_DOMAIN=$(az containerapp revision show \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
-    --revision <GREEN_REVISION_NAME> \
+    --resource-group <resource-group> \
+    --name <app-name> \
+    --revision <green-revision-name> \
     --query "properties.fqdn" \
-    --output tsv \
-    | tr -d '\r\n')
+    --output tsv)
 
-curl -s http://$GREEN_DOMAIN
+curl -s https://$GREEN_DOMAIN
 ```
 
 Use the following commands to test with the label-specific fully qualified domain name (FQDN):
 
 ```azurecli
+export APP_NAME=<app-name>
+
 # Get the containerapp environment default domain
-export APP_DOMAIN=$(az containerapp env show \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_ENVIRONMENT_NAME> \
+export APP_ENVIRONMENT_DOMAIN=$(az containerapp env show \
+    --resource-group <resource-group> \
+    --name <app-environment-name> \
     --query "properties.defaultDomain" \
-    --output tsv \
-    | tr -d '\r\n')
+    --output tsv)
 
 # Test the production FQDN
-curl -s https://$APP_NAME.$APP_DOMAIN
+curl -s https://$APP_NAME.$APP_ENVIRONMENT_DOMAIN
 
 # Test the blue label FQDN
-curl -s https://$APP_NAME---blue.$APP_DOMAIN
+curl -s https://$APP_NAME---blue.$APP_ENVIRONMENT_DOMAIN
 
 # Test the green label FQDN
-curl -s https://$APP_NAME---green.$APP_DOMAIN
+curl -s https://$APP_NAME---green.$APP_ENVIRONMENT_DOMAIN
 ```
 
 ## Send production traffic to the green revision
@@ -121,18 +119,18 @@ To switch production traffic to the green revision, use the following commands:
 ```azurecli
 # switch based on revision name
 az containerapp ingress traffic set \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
-    --revision-weight <BLUE_REVISION_NAME>=0 <GREEN_REVISION_NAME>=100
+    --resource-group <resource-group> \
+    --name <app-name> \
+    --revision-weight <blue-revision-name>=0 <green-revision-name>=100
 
 # switch based on label
 az containerapp ingress traffic set \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
+    --resource-group <resource-group> \
+    --name <app-name> \
     --label-weight blue=0 green=100
 ```
 
-Ensure that the total label weight doesn't exceed 100.
+Ensure that the total label weight equals 100%.
 
 Azure Container Apps not only enables you to switch traffic between blue-green deployments but also between multiple revisions. You can also redirect a specific amount of production traffic to the green deployment.
 
@@ -146,9 +144,8 @@ To enable traffic splitting when using Spring Cloud Gateway, you need to set the
 
 ```azurecli
 az containerapp show \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
+    --resource-group <resource-group> \
+    --name <app-name> \
     --query "properties.configuration.ingress.fqdn" \
-    --output tsv \
-    | tr -d '\r\n'
+    --output tsv
 ```

articles/spring-apps/migration/migrate-to-azure-container-apps-overview.md

@@ -1,12 +1,12 @@
 ---
 title: Migrate to Azure Container Apps
-description: Describes an overview approach of migrating to Azure Container Apps.
+description: Describes migrating to Azure Container Apps.
 author: KarlErickson
 ms.author: karler
-ms.reviewer: dixue
+ms.reviewer: dingmeng-xue
 ms.service: azure-spring-apps
 ms.topic: upgrade-and-migration-article
-ms.date: 01/29/2025
+ms.date: 03/17/2025
 ms.custom: devx-track-java, devx-track-extended-java
 ---
 
@@ -78,6 +78,56 @@ The migration approach from Azure Spring Apps to Azure Container Apps involves t
 
 1. Client and automation tools: To streamline daily development and operational tasks, take advantage of client tools and automation solutions. These tools include the Azure CLI, Azure DevOps, GitHub Actions, and extensions in client tools or IDEs. These tools can help automate deployments, monitor performance, and manage resources efficiently, reducing manual effort and enhancing operational agility. To learn about popular tools, see [Clients or automation tools for Azure Container Apps](./migrate-to-azure-container-apps-automation.md).
 
+## Migration assistant tool
+
+To speed up your migration and help you evaluate features on Azure Container Apps, we provide a new command in the Azure CLI. This command retrieves the configurations of existing Azure Spring Apps resources based on the resource ID of the service instance. It then translates these configurations into Bicep files for Azure Container App resources. This method enables you to quickly set up an Azure Container Apps managed environment and app resources while applying basic settings similar to those settings in your existing Azure Spring Apps resources. For more information, see [az spring export](/cli/azure/spring#az-spring-export).
+
+To create Azure Container Apps resources that match the configurations of your existing Azure Spring Apps resources, use the following steps:
+
+1. Install Azure CLI version 2.45.0 or higher and the latest version of the Azure Spring Apps extension by using the `az extension add --name spring` command.
+
+1. Generate Bicep files to create the corresponding Azure Container Apps resources by using the following command:
+
+    ```azurecli
+    az spring export \
+        --resource-group <resource-group-name> \
+        --target aca \
+        --subscription <subscription-id> \
+        --service <service-name> \
+        --output-folder <output-folder-name> 
+    ```
+
+1. The previous command generates a **README.md** file with detailed instructions. Follow those instructions to update the required parameters in the Bicep files.
+
+   > [!NOTE]
+   > Azure Container Apps requires containerized image URLs. If you don't yet have a containerized image URL for your application, you can leave the quickstart image URL in the parameters unchanged, and deploy your own application later. For more information on obtaining container images, see [Overview of containerization](./migrate-to-azure-container-apps-build-overview.md)
+
+1. If a resource group doesn't exist, create it by using the following command:
+
+    ```azurecli
+    az group create \
+        --name <resource-group-name> \
+        --subscription <subscription-id> \
+        --location <location> 
+    ```
+
+1. Deploy Azure Container Apps resources to the resource group by using the following command:
+
+    > [!NOTE]
+    > You might need to run the command multiple times and adjust the configuration based on the response message.
+
+    ```azurecli
+    az deployment group create \
+      --resource-group <resource-group-name> \
+      --template-file main.bicep \
+      --parameters param.bicepparam \
+      --subscription <subscription-id>
+    ```
+
+1. Follow the instructions in the **README.md** file to update resources for advanced features. These features include uploading certificates, enabling a custom domain, adding role assignments to the system-assigned managed identity, and more.
+
+1. If you need the Terraform configuration of those resources, export them using the export workflow of the Azure Terraform Resource Provider. For more information, see [Overview of the Azure Terraform Resource Provider](/azure/developer/terraform/azure-terraform-resource-provider/resource-provider-overview).
+
 ## Tutorial
 
 We provide a tutorial to demonstrate the end-to-end experience of running the ACME Fitness Store application on Azure Container Apps. For more information, see [acme-fitness-store/azure-container-apps](https://github.com/Azure-Samples/acme-fitness-store/tree/Azure/azure-container-apps). This tutorial offers hands-on guidance, helping you quickly gain practical insights and confidence in deploying and managing containerized applications on the platform.