Add migration tooling and update blue-green deployment

dingmeng-xue · dingmeng-xue · commit 9103dad0b074 · 2025-03-13T14:03:30.000+08:00
diff --git a/articles/spring-apps/migration/migrate-to-azure-container-apps-blue-green.md b/articles/spring-apps/migration/migrate-to-azure-container-apps-blue-green.md
@@ -3,21 +3,16 @@ title: The Experience of Blue-Green Deployment in Azure Container Apps
 description: Describes the experience of blue-green deployment in Azure Container Apps.
 author: KarlErickson
 ms.author: karler
-ms.reviewer: dixue
 ms.service: azure-spring-apps
 ms.topic: upgrade-and-migration-article
-ms.date: 01/29/2025
+ms.date: 11/18/2024
 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)]
+# The Experience of Blue-Green Deployment in 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
@@ -57,66 +52,60 @@ az containerapp update \
     --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 command:
 
 ```azurecli
 az containerapp revision label add \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
-    --label blue \
-    --revision <APP_NAME>--<BLUE_SUFFIX>
+  --name <APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
+  --label blue \
+  --revision <BLUE_REVISION_NAME>
 
 az containerapp revision label add \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
-    --label green \
-    --revision <APP_NAME>--<GREEN_SUFFIX>
+  --name <APP_NAME> \
+  --resource-group <RESOURCE_GROUP> \
+  --label green \
+  --revision <GREEN_REVISION_NAME>
 ```
+Here, `<BLUE_REVISION_NAME>` is `<APP_NAME>--<BLUE_SUFFIX>`, and `<GREEN_REVISION_NAME>` is `<APP_NAME>--<GREEN_SUFFIX>`. A label can only be assigned 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.
 
-## Test a new revision
+## Test new revision
 
-Each revision in Azure Container Apps has its own URL, enabling you to test and verify your deployment against the specific URL. Use the following commands to test the green revision with a specific domain, even though all production traffic is directed to the blue revision:
+Each revision in Azure Container Apps has its own URL, enabling you to test and verify your deployment against the specific URL. Test the green revision with a specific domain, even though all production traffic is directed to the blue revision:
 
 ```azurecli
-export GREEN_DOMAIN=$(az containerapp revision show \
-    --resource-group <RESOURCE_GROUP> \
-    --name <APP_NAME> \
-    --revision <GREEN_REVISION_NAME> \
-    --query "properties.fqdn" \
-    --output tsv \
-    | tr -d '\r\n')
+GREEN_DOMAIN=$(az containerapp revision show --resource-group <RESOURCE_GROUP> --name <APP_NAME> --revision <GREEN_REVISION_NAME> --query "properties.fqdn" -o 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):
+Additionally, test with the label-specific FQDN:
 
 ```azurecli
 # Get the containerapp environment default domain
-export APP_DOMAIN=$(az containerapp env show \
+export APP_ENV_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_ENV_DOMAIN
 
-# Test the blue label FQDN
-curl -s https://$APP_NAME---blue.$APP_DOMAIN
+# Test the blue lable FQDN
+curl -s https://$APP_NAME---blue.$APP_ENV_DOMAIN
 
-# Test the green label FQDN
-curl -s https://$APP_NAME---green.$APP_DOMAIN
+# Test the green lable FQDN
+curl -s https://$APP_NAME---green.$APP_ENV_DOMAIN
 ```
 
 ## Send production traffic to the green revision
 
-To switch production traffic to the green revision, use the following commands:
+To switch production traffic to the green revision, use the following command:
 
 ```azurecli
 # switch based on revision name
@@ -132,23 +121,22 @@ az containerapp ingress traffic set \
     --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.
+Azure Container Apps not only allows you to switch traffic between blue-green deployments but also between multiple revisions. Additionally, you can redirect a specific amount of production traffic to the green deployment.
 
 For more information about blue-green deployment in Azure Container Apps, see [Blue-Green Deployment in Azure Container Apps](../../container-apps/blue-green-deployment.md).
 
 ## Limitation
 
 The Eureka Server isn't suitable for blue-green deployment because all revisions of the app are registered with the Eureka Server, preventing effective traffic splitting.
 
-To enable traffic splitting when using Spring Cloud Gateway, you need to set the application URL in the URI field of your gateway configuration. You can obtain the application URL by using the following command:
+To enable traffic splitting when using Spring Cloud Gateway, you need to set the application URL in the URI field of your gateway configuration. You can obtain the application URL using the following command:
 
 ```azurecli
 az containerapp show \
     --resource-group <RESOURCE_GROUP> \
     --name <APP_NAME> \
     --query "properties.configuration.ingress.fqdn" \
-    --output tsv \
-    | tr -d '\r\n'
-```
+    --output tsv
+```
diff --git a/articles/spring-apps/migration/migrate-to-azure-container-apps-overview.md b/articles/spring-apps/migration/migrate-to-azure-container-apps-overview.md
@@ -78,6 +78,38 @@ 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 Azure CLI. This command retrieves the configurations of existing Azure Spring Apps resource based on the resource id of service instance and translates them into Biceps files for Azure Container App resources. This method allows you to quickly set up an Azure Container Apps managed environment and applications while applying basic settings similar to those in your Azure Spring Apps. For more details, refer to the following steps or see [az spring export](/cli/azure/spring#az-spring-export)
+
+1. Install Azure CLI version 2.45.0 or higher and latest version of Azure Spring Apps extension using the following command `az extension add --name spring`.
+1. Generate Bicep files to create the corresponding Azure Container Apps resources. It also generates a `README.md` file with detailed instructions.
+   ```azurecli
+   az spring export \ 
+       --target aca \
+       --subscription <subscription-id> \
+       --resource-group <resource-group-name> \
+       --service <service-name> \
+       --output-folder <output-folder-name> 
+   ```
+1. Follow the instructions in `README.md` to update the required parameters in the Bicep files.
+1. Create a resource group if it doesn't exist.
+   ```azurecli
+   az group create \
+       --subscription <subscription-id> \
+       --name <resource-group-name> \
+       --location <location> 
+   ```
+1. Deploy Azure Container Apps resources to the resource group. You may 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 `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.
+
+If you need the Terraform configuration of those resources, you can export them using the export workflow of 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.
