Merge pull request #258979 from ggailey777/upgrade-all-langs

[Functions] Expand worker update article to all languages

Author: American-Dipper

.openpublishing.redirection.json

@@ -9622,6 +9622,11 @@
             "redirect_url": "/azure/azure-functions/functions-reference-python?pivots=python-mode-decorators#triggers-and-inputs",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-functions/update-java-versions.md",
+            "redirect_url": "/azure/azure-functions/update-language-versions",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/azure-government/documentation-government-k8.md",
             "redirect_url": "/azure/azure-government",

articles/azure-functions/TOC.yml

@@ -568,8 +568,9 @@
           items:
             - name: Migrate to model v4.x
               href: functions-node-upgrade-v4.md
-        - name: Update Java versions
-          href: update-java-versions.md  
+        - name: Update language versions
+          href: update-language-versions.md  
+          displayName: upgrade, migrate, language stack
     - name: Monitor
       items:
         - name: Monitor function apps with Azure Monitor

articles/azure-functions/functions-deployment-slots.md

@@ -6,25 +6,25 @@ ms.date: 03/02/2022
 ---
 # Azure Functions deployment slots
 
-Azure Functions deployment slots allow your function app to run different instances called "slots". Slots are different environments exposed via a publicly available endpoint. One app instance is always mapped to the production slot, and you can swap instances assigned to a slot on demand. Function apps running under the Apps Service plan may have multiple slots, while under the Consumption plan only one slot is allowed.
+Azure Functions deployment slots allow your function app to run different instances called _slots_. Slots are different environments exposed via a publicly available endpoint. One app instance is always mapped to the production slot, and you can swap instances assigned to a slot on demand. Function apps running in a [Consumption plan](./consumption-plan.md) have a single extra slot for staging. You can obtain more staging slots by running your app in a [Premium plan](./functions-premium-plan.md) or [Dedicated (App Service) plan](./dedicated-plan.md). For more information, see [Service limits](./functions-scale.md#service-limits). 
 
 The following reflect how functions are affected by swapping slots:
 
-- Traffic redirection is seamless; no requests are dropped because of a swap. This seamless behavior is a result of the next function triggers being routed to the swapped slot.
-- Currently executing function are terminated during the swap. Please review [Improve the performance and reliability of Azure Functions](performance-reliability.md#write-functions-to-be-stateless) to learn how to write stateless and defensive functions.
+- Traffic redirection is seamless; no requests are dropped because of a swap. This seamless behavior occurs because the next function trigger is routed to the swapped slot.
+- Currently executing function are terminated during the swap. To learn how to write stateless and defensive functions, see [Improve the performance and reliability of Azure Functions](performance-reliability.md#write-functions-to-be-stateless).
 
 ## Why use slots?
 
-There are a number of advantages to using deployment slots. The following scenarios describe common uses for slots:
+There are many advantages to using deployment slots, including:
 
 - **Different environments for different purposes**: Using different slots gives you the opportunity to differentiate app instances before swapping to production or a staging slot.
 - **Prewarming**: Deploying to a slot instead of directly to production allows the app to warm up before going live. Additionally, using slots reduces latency for HTTP-triggered workloads. Instances are warmed up before deployment, which reduces the cold start for newly deployed functions.
 - **Easy fallbacks**: After a swap with production, the slot with a previously staged app now has the previous production app. If the changes swapped into the production slot aren't as you expect, you can immediately reverse the swap to get your "last known good instance" back.
-- **Minimize restarts**: Changing app settings in a production slot requires a restart of the running app. You can instead change settings in a staging slot and swap the settings change into production with a prewarmed instance. This is the recommended way to upgrade between Functions runtime versions while maintaining the highest availability. To learn more, see [Minimum downtime upgrade](migrate-version-3-version-4.md#minimum-downtime-upgrade). 
+- **Minimize restarts**: Changing app settings in a production slot requires a restart of the running app. You can instead change settings in a staging slot and swap the settings change into production with a prewarmed instance. Slots are the recommended way to upgrade between Functions runtime versions while maintaining the highest availability. To learn more, see [Minimum downtime upgrade](migrate-version-3-version-4.md#minimum-downtime-upgrade). 
 
 ## Swap operations
 
-During a swap, one slot is considered the source and the other the target. The source slot has the instance of the application that is applied to the target slot. The following steps ensure the target slot doesn't experience downtime during a swap:
+During a swap, one slot is considered the source and the other is the target. The source slot has the instance of the application that is applied to the target slot. The following steps ensure the target slot doesn't experience downtime during a swap:
 
 1. **Apply settings:** Settings from the target slot are applied to all instances of the source slot. For example, the production settings are applied to the staging instance. The applied settings include the following categories:
     - [Slot-specific](#manage-settings) app settings and connection strings (if applicable)
@@ -33,9 +33,9 @@ During a swap, one slot is considered the source and the other the target. The s
 
 1. **Wait for restarts and availability:** The swap waits for every instance in the source slot to complete its restart and to be available for requests. If any instance fails to restart, the swap operation reverts all changes to the source slot and stops the operation.
 
-1. **Update routing:** If all instances on the source slot are warmed up successfully, the two slots complete the swap by switching routing rules. After this step, the target slot (for example, the production slot) has the app that's previously warmed up in the source slot.
+1. **Update routing:** If all instances on the source slot are warmed up successfully, the two slots complete the swap by switching routing rules. After this step, the target slot (for example, the production slot) has the app that was previously warmed up in the source slot.
 
-1. **Repeat operation:** Now that the source slot has the pre-swap app previously in the target slot, complete the same operation by applying all settings and restarting the instances for the source slot.
+1. **Repeat operation:** Now that the source slot has the preswap app previously in the target slot, complete the same operation by applying all settings and restarting the instances for the source slot.
 
 Keep in mind the following points:
 
@@ -53,7 +53,7 @@ Some configuration settings are slot-specific. The following lists detail which
 
 - Publishing endpoints
 - Custom domain names
-- Non-public certificates and TLS/SSL settings
+- Nonpublic certificates and TLS/SSL settings
 - Scale settings
 - IP restrictions
 - Always On
@@ -73,15 +73,15 @@ Some configuration settings are slot-specific. The following lists detail which
 - Service endpoints *
 - Azure Content Delivery Network *
 
-Features marked with an asterisk (*) are planned to be unswapped.
+Features marked with an asterisk (*) don't get swapped, by design.
 
 > [!NOTE]
 > Certain app settings that apply to unswapped settings are also not swapped. For example, since diagnostic settings are not swapped, related app settings like `WEBSITE_HTTPLOGGING_RETENTION_DAYS` and `DIAGNOSTICS_AZUREBLOBRETENTIONDAYS` are also not swapped, even if they don't show up as slot settings.
 >
 
 ### Create a deployment setting
 
-You can mark settings as a deployment setting, which makes it "sticky". A sticky setting doesn't swap with the app instance.
+You can mark settings as a deployment setting, which makes it _sticky_. A sticky setting doesn't swap with the app instance.
 
 If you create a deployment setting in one slot, make sure to create the same setting with a unique value in any other slot that is involved in a swap. This way, while a setting's value doesn't change, the setting names remain consistent among slots. This name consistency ensures your code doesn't try to access a setting that is defined in one slot but not another.
 
@@ -114,9 +114,35 @@ All slots scale to the same number of workers as the production slot.
 - For Consumption plans, the slot scales as the function app scales.
 - For App Service plans, the app scales to a fixed number of workers. Slots run on the same number of workers as the app plan.
 
+## View slots
+
+You can view information about existing slots using either the [Azure CLI](/cli/azure) or through the [Azure portal](https://portal.azure.com).
+
+### [Azure portal](#tab/azure-portal)
+
+Use these steps to create a new slot in the portal:
+
+1. Navigate to your function app.
+
+1. Select **Deployment slots** and the existing slots are shown. 
+ 
+### [Azure CLI](#tab/azure-cli)
+
+Run this [az functionapp deployment slot list](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-list) command to list the existing slots in your function app:
+
+```azurecli
+az functionapp deployment slot list --name "<APP_NAME>" --resource-group "<RESOURCE_GROUP>"
+```
+
+---
+
 ## Add a slot
 
-You can add a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-create) or through the portal. The following steps demonstrate how to create a new slot in the portal:
+You can add a slot using either the [Azure CLI](/cli/azure) or through the [Azure portal](https://portal.azure.com). 
+
+### [Azure portal](#tab/azure-portal)
+
+Use these steps to create a slot in the portal:
 
 1. Navigate to your function app.
 
@@ -128,11 +154,30 @@ You can add a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az-funct
 
     :::image type="content" source="./media/functions-deployment-slots/functions-deployment-slots-add-name.png" alt-text="Name the Azure Functions deployment slot." border="true":::
 
+### [Azure CLI](#tab/azure-cli)
+
+Run the [az functionapp deployment slot create](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-create) command to create a slot named `staging` in your function app:
+
+```azurecli
+az functionapp deployment slot create --name "<APP_NAME>" --resource-group "<RESOURCE_GROUP>" --slot staging
+```
+
+---
+
+## Access slot resources
+
+You access resources (HTTP triggers and administrator endpoints) in a staging slot in the same way as the production slot. However, instead of the function app host name you use the slot-specific host name in the request URL, along with any slot-specific keys. Because staging slots are live apps, you must [secure your functions](./security-concepts.md) in a staging slot as you would in the production slot.  
+
 ## Swap slots
 
-You can swap slots via the [CLI](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-swap) or through the portal. The following steps demonstrate how to swap slots in the portal:
+You can swap slots in an out of production using either the [Azure CLI](/cli/azure) or through the [Azure portal](https://portal.azure.com). 
+
+### [Azure portal](#tab/azure-portal)
+
+Use these steps to swap a staging slot into production:
 
 1. Navigate to the function app.
+
 1. Select **Deployment slots**, and then select **Swap**.
 
     :::image type="content" source="./media/functions-deployment-slots/functions-swap-deployment-slot.png" alt-text="Screenshot that shows the 'Deployment slot' page with the 'Add Slot' action selected." border="true":::
@@ -141,15 +186,28 @@ You can swap slots via the [CLI](/cli/azure/functionapp/deployment/slot#az-funct
 
     :::image type="content" source="./media/functions-deployment-slots/azure-functions-deployment-slots-swap-config.png" alt-text="Swap the deployment slot." border="true":::
 
-The operation may take a moment while the swap operation is executing.
+The swap operation can take a few seconds.
+
+### [Azure CLI](#tab/azure-cli)
+
+Run this [az functionapp deployment slot swap](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-swap) command to swap between a slot named `staging` and the production slot in your function app:
+
+```azurecli
+az functionapp deployment slot swap --name "<APP_NAME>" --resource-group "<RESOURCE_GROUP>" --slot staging --target-slot production
+```  
+---
 
 ## Roll back a swap
 
-If a swap results in an error or you simply want to "undo" a swap, you can roll back to the initial state. To return to the pre-swapped state, do another swap to reverse the swap.
+If a swap results in an error or you simply want to "undo" a swap, you can roll back to the initial state. To return to the preswapped state, do another swap to reverse the swap.
 
 ## Remove a slot
 
-You can remove a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-delete) or through the portal. The following steps demonstrate how to remove a slot in the portal:
+You can remove a slot using either the [Azure CLI](/cli/azure) or through the [Azure portal](https://portal.azure.com). 
+
+### [Azure portal](#tab/azure-portal)
+
+Use these steps to remove a slot from your app in the portal:
 
 1. Navigate to **Deployment slots** in the function app, and then select the slot name.
 
@@ -163,19 +221,19 @@ You can remove a slot via the [CLI](/cli/azure/functionapp/deployment/slot#az-fu
 
     :::image type="content" source="./media/functions-deployment-slots/functions-delete-deployment-slot-details.png" alt-text="Delete the deployment slot in the Azure portal." border="true":::
 
-1. Close the delete confirmation pane.
+1. Close the confirmation pane.
 
     :::image type="content" source="./media/functions-deployment-slots/functions-deployment-slot-deleted.png" alt-text="Deployment slot delete confirmation." border="true":::
 
-## Automate slot management
+### [Azure CLI](#tab/azure-cli)
+
+Run the [az functionapp deployment slot delete](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-delete) command to remove a slot named `staging` from your function app:
 
-Using the [Azure CLI](/cli/azure/functionapp/deployment/slot), you can automate the following actions for a slot:
+```azurecli
+az functionapp deployment slot delete --name "<APP_NAME>" --resource-group "<RESOURCE_GROUP>" --slot staging
+```
 
-- [create](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-create)
-- [delete](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-delete)
-- [list](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-list)
-- [swap](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-swap)
-- [auto-swap](/cli/azure/functionapp/deployment/slot#az-functionapp-deployment-slot-auto-swap)
+---
 
 ## Change App Service plan
 
@@ -202,7 +260,7 @@ Use the following steps to change a slot's App Service plan:
 
 Azure Functions deployment slots have the following considerations:
 
-- The number of slots available to an app depends on the plan. The Consumption plan is only allowed one deployment slot. Additional slots are available for apps running under other plans. For details, see [Service limits](functions-scale.md#service-limits).
+- The number of slots available to an app depends on the plan. The Consumption plan is only allowed one deployment slot. More slots are available for apps running under other plans. For details, see [Service limits](functions-scale.md#service-limits).
 - Swapping a slot resets keys for apps that have an `AzureWebJobsSecretStorageType` app setting equal to `files`.
 - When slots are enabled, your function app is set to read-only mode in the portal.
 - Use function app names shorter than 32 characters. Names longer than 32 characters are at risk of causing [host ID collisions](storage-considerations.md#host-id-considerations).