Merge pull request #284886 from ecfan/dotnet

prmerger-automator[bot] · web-flow · commit fbed7dd1203e · 2024-08-16T19:30:44.000Z
[Standard[ Change to 'dotnet' for language worker runtime (FUNCTIONS_WORKER_RUNTIME)
diff --git a/articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md b/articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md
@@ -439,7 +439,7 @@ The following example describes a sample Azure Arc-enabled Logic Apps resource d
             },
             {
                "name": "FUNCTIONS_WORKER_RUNTIME",
-               "value": "node"
+               "value": "dotnet"
             },
             {
                "name": "AzureWebJobsStorage",
@@ -537,7 +537,7 @@ The following example describes a sample Azure Arc-enabled Logic Apps resource d
             },
             {
                "name": "FUNCTIONS_WORKER_RUNTIME",
-               "value": "node"
+               "value": "dotnet"
             },
             {
                "name": "AzureWebJobsStorage",
@@ -575,6 +575,14 @@ The following example describes a sample Azure Arc-enabled Logic Apps resource d
 }
 ```
 
+> [!NOTE]
+> 
+> Previously, the **FUNCTIONS_WORKER_RUNTIME** setting's default value was **`node`**. 
+> Now, **`dotnet`** is the default value for all new and existing deployed Standard 
+> logic apps, even for apps that had a different value. This change shouldn't affect 
+> your workflow's runtime, and everything should work the same way as before. For more 
+> information, see the [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
+
 <a name="include-app-service-plan"></a>
 
 ### Include App Service plan with deployment
diff --git a/articles/logic-apps/create-single-tenant-workflows-azure-portal.md b/articles/logic-apps/create-single-tenant-workflows-azure-portal.md
@@ -129,6 +129,14 @@ More workflows in your logic app raise the risk of longer load times, which nega
 
    :::image type="content" source="media/create-single-tenant-workflows-azure-portal/create-logic-app-basics.png" alt-text="Screenshot shows Azure portal and page named Create Logic App Workflow Service Plan." lightbox="media/create-single-tenant-workflows-azure-portal/create-logic-app-basics.png":::
 
+   > [!NOTE]
+   > 
+   > By default, the language worker runtime value for your Standard logic app is **`dotnet`**. 
+   > Previously, **`node`** was the default value. However, **`dotnet`** is now the default value 
+   > for all new and existing deployed Standard logic apps, even for apps that had a different value. 
+   > This change shouldn't affect your workflow's runtime, and everything should work the same way 
+   > as before. For more information, see the [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
+
 1. When you finish, select **Next: Storage**.
 
 1. On the **Storage** tab, provide the following information about the storage solution and hosting plan to use for your logic app.
diff --git a/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md b/articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md
@@ -624,7 +624,7 @@ To locally run webhook-based triggers and actions in Visual Studio Code, you nee
       "IsEncrypted": false,
       "Values": {
          "AzureWebJobsStorage": "UseDevelopmentStorage=true",
-         "FUNCTIONS_WORKER_RUNTIME": "node",
+         "FUNCTIONS_WORKER_RUNTIME": "dotnet",
          "FUNCTIONS_V2_COMPATIBILITY_MODE": "true",
          <...>
          "Workflows.WebhookRedirectHostUri": "http://xxxXXXXxxxXXX.ngrok.io",
@@ -633,6 +633,14 @@ To locally run webhook-based triggers and actions in Visual Studio Code, you nee
    }
    ```
 
+   > [!NOTE]
+   > 
+   > Previously, the **FUNCTIONS_WORKER_RUNTIME** setting's default value was **`node`**. 
+   > Now, **`dotnet`** is the default value for all new and existing deployed Standard 
+   > logic apps, even for apps that had a different value. This change shouldn't affect 
+   > your workflow's runtime, and everything should work the same way as before. For more 
+   > information, see the [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
+
 The first time when you start a local debugging session or run the workflow without debugging, the Azure Logic Apps runtime registers the workflow with the service endpoint and subscribes to that endpoint for notifying the webhook operations. The next time that your workflow runs, the runtime won't register or resubscribe because the subscription registration already exists in local storage.
 
 When you stop the debugging session for a workflow run that uses locally run webhook-based triggers or actions, the existing subscription registrations aren't deleted. To unregister, you have to manually remove or delete the subscription registrations.
@@ -968,7 +976,7 @@ Deployment for the Standard logic app resource requires a hosting plan and prici
             "IsEncrypted": false,
             "Values": {
                "AzureWebJobsStorage": "UseDevelopmentStorage=true",
-               "FUNCTIONS_WORKER_RUNTIME": "node",
+               "FUNCTIONS_WORKER_RUNTIME": "dotnet",
                "APPINSIGHTS_INSTRUMENTATIONKEY": <instrumentation-key>
             }
          }
@@ -1237,7 +1245,7 @@ To debug a stateless workflow more easily, you can enable the run history for th
       "IsEncrypted": false,
       "Values": {
          "AzureWebJobsStorage": "UseDevelopmentStorage=true",
-         "FUNCTIONS_WORKER_RUNTIME": "node",
+         "FUNCTIONS_WORKER_RUNTIME": "dotnet",
          "Workflows.{yourWorkflowName}.OperationOptions": "WithStatelessRunHistory"
       }
    }
@@ -1251,7 +1259,7 @@ To debug a stateless workflow more easily, you can enable the run history for th
       "Values": {
          "AzureWebJobsStorage": "DefaultEndpointsProtocol=https;AccountName=fabrikamstorageacct; \
              AccountKey=<access-key>;EndpointSuffix=core.windows.net",
-         "FUNCTIONS_WORKER_RUNTIME": "node",
+         "FUNCTIONS_WORKER_RUNTIME": "dotnet",
          "Workflows.{yourWorkflowName}.OperationOptions": "WithStatelessRunHistory"
       }
    }
diff --git a/articles/logic-apps/edit-app-settings-host-settings.md b/articles/logic-apps/edit-app-settings-host-settings.md
@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 03/08/2024
+ms.date: 08/16/2024
 ms.custom: fasttrack-edit
 ---
 
@@ -55,7 +55,7 @@ App settings in Azure Logic Apps work similarly to app settings in Azure Functio
 | Setting | Default value | Description |
 |---------|---------------|-------------|
 | `AzureWebJobsStorage` | None | Sets the connection string for an Azure storage account. For more information, see [AzureWebJobsStorage](../azure-functions/functions-app-settings.md#azurewebjobsstorage) |
-| `FUNCTIONS_WORKER_RUNTIME` | `node` | Sets the language worker runtime to use with your logic app resource and workflows. However, this setting is no longer necessary due to automatically enabled multi-language support. <br><br>For more information, see [FUNCTIONS_WORKER_RUNTIME](../azure-functions/functions-app-settings.md#functions_worker_runtime). |
+| `FUNCTIONS_WORKER_RUNTIME` | `dotnet` | Sets the language worker runtime to use with your logic app resource and workflows. However, this setting is no longer necessary due to automatically enabled multi-language support. <br><br>**Note**: Previously, this setting's default value was **`node`**. Now, **`dotnet`** is the default value for all new and existing deployed Standard logic apps, even for apps that had a different different value. This change shouldn't affect your workflow's runtime, and everything should work the same way as before.<br><br>For more information, see [FUNCTIONS_WORKER_RUNTIME](../azure-functions/functions-app-settings.md#functions_worker_runtime). |
 | `ServiceProviders.Sftp.FileUploadBufferTimeForTrigger` | `00:00:20` <br>(20 seconds) | Sets the buffer time to ignore files that have a last modified timestamp that's greater than the current time. This setting is useful when large file writes take a long time and avoids fetching data for a partially written file. |
 | `ServiceProviders.Sftp.OperationTimeout` | `00:02:00` <br>(2 min) | Sets the time to wait before timing out on any operation. |
 | `ServiceProviders.Sftp.ServerAliveInterval` | `00:30:00` <br>(30 min) | Sends a "keep alive" message to keep the SSH connection active if no data exchange with the server happens during the specified period. |
diff --git a/articles/logic-apps/enterprise-integration/create-integration-account.md b/articles/logic-apps/enterprise-integration/create-integration-account.md
@@ -274,7 +274,7 @@ Before you can link your integration account to a Standard logic app resource, y
        "IsEncrypted": false,
        "Values": {
            "AzureWebJobStorage": "UseDevelopmentStorage=true",
-           "FUNCTIONS_WORKER_RUNTIME": "node",
+           "FUNCTIONS_WORKER_RUNTIME": "dotnet",
            "WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL": "https://prod-03.westus.logic.azure.com:443/integrationAccounts/...."
        }
    }

Original file line number	Diff line number	Diff line change
`@@ -439,7 +439,7 @@ The following example describes a sample Azure Arc-enabled Logic Apps resource d`
`439`	`439`	`},`
`440`	`440`	`{`
`441`	`441`	`"name": "FUNCTIONS_WORKER_RUNTIME",`
`442`		`- "value": "node"`
	`442`	`+ "value": "dotnet"`
`443`	`443`	`},`
`444`	`444`	`{`
`445`	`445`	`"name": "AzureWebJobsStorage",`
`@@ -537,7 +537,7 @@ The following example describes a sample Azure Arc-enabled Logic Apps resource d`
`537`	`537`	`},`
`538`	`538`	`{`
`539`	`539`	`"name": "FUNCTIONS_WORKER_RUNTIME",`
`540`		`- "value": "node"`
	`540`	`+ "value": "dotnet"`
`541`	`541`	`},`
`542`	`542`	`{`
`543`	`543`	`"name": "AzureWebJobsStorage",`
`@@ -575,6 +575,14 @@ The following example describes a sample Azure Arc-enabled Logic Apps resource d`
`575`	`575`	`}`
`576`	`576`	```
`577`	`577`
	`578`	`+> [!NOTE]`
	`579`	`+>`
	`580`	+> Previously, the FUNCTIONS_WORKER_RUNTIME setting's default value was `node`.
	`581`	+> Now, `dotnet` is the default value for all new and existing deployed Standard
	`582`	`+> logic apps, even for apps that had a different value. This change shouldn't affect`
	`583`	`+> your workflow's runtime, and everything should work the same way as before. For more`
	`584`	`+> information, see the [FUNCTIONS_WORKER_RUNTIME app setting](edit-app-settings-host-settings.md#reference-local-settings-json).`
	`585`	`+`
`578`	`586`	`<a name="include-app-service-plan"></a>`
`579`	`587`
`580`	`588`	`### Include App Service plan with deployment`
Original file line number	Diff line number	Diff line change
`@@ -274,7 +274,7 @@ Before you can link your integration account to a Standard logic app resource, y`
`274`	`274`	`"IsEncrypted": false,`
`275`	`275`	`"Values": {`
`276`	`276`	`"AzureWebJobStorage": "UseDevelopmentStorage=true",`
`277`		`- "FUNCTIONS_WORKER_RUNTIME": "node",`
	`277`	`+ "FUNCTIONS_WORKER_RUNTIME": "dotnet",`
`278`	`278`	`"WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL": "https://prod-03.westus.logic.azure.com:443/integrationAccounts/...."`
`279`	`279`	`}`
`280`	`280`	`}`