Skip to content

Commit ab622b9

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #285898 from ecfan/appkind
Add info that "APP_KIND" app setting must be set to "workflowApp"
2 parents 7957672 + 3b20984 commit ab622b9

4 files changed

+42
-1
lines changed

‎articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -465,6 +465,22 @@ The following example describes a sample Azure Arc-enabled Logic Apps resource d
465465
}
466466
```
467467

468+
> [!NOTE]
469+
>
470+
> By default, **FUNCTIONS_WORKER_RUNTIME** app setting for your logic app is **`dotnet`**.
471+
> Previously, **`node`** was the default value. However, **`dotnet`** is now the default
472+
> value for all new and existing deployed Arc enabled logic apps, even for apps that had
473+
> a different value. This change shouldn't affect your workflow's runtime, and everything
474+
> should work the same way as before. For more information, see the
475+
> [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
476+
>
477+
> The **APP_KIND** app setting for your logic app is set to **workflowapp**, but in some scenarios,
478+
> this app setting is missing, for example, due to Azure Resource Manager templates or other scenarios
479+
> where the setting might not be included. If certain actions don't work, such as the
480+
> **Execute JavaScript Code** action or the workflow stops working, check that the
481+
> **APP_KIND** app setting exists and is set to to **workflowapp**. For more information, see the
482+
> [**APP_KIND** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
483+
468484
### Container deployment
469485

470486
If you prefer to use container tools and deployment processes, you can containerize your logic apps and deploy them to Azure Arc-enabled Logic Apps. For this scenario, complete the following high-level tasks when you set up your infrastructure:

‎articles/logic-apps/create-single-tenant-workflows-azure-portal.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -138,6 +138,13 @@ More workflows in your logic app raise the risk of longer load times, which nega
138138
> for all new and existing deployed Standard logic apps, even for apps that had a different value.
139139
> This change shouldn't affect your workflow's runtime, and everything should work the same way
140140
> as before. For more information, see the [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
141+
>
142+
> The **APP_KIND** app setting for your Standard logic app is set to **workflowApp**, but in some
143+
> scenarios, this app setting is missing, for example, due to automation using Azure Resource Manager
144+
> templates or other scenarios where the setting isn't included. If certain actions don't work,
145+
> such as the **Execute JavaScript Code** action or the workflow stops working, check that the
146+
> **APP_KIND** app setting exists and is set to to **workflowApp**. For more information, see the
147+
> [**APP_KIND** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
141148
142149
1. When you finish, select **Next: Storage**.
143150

‎articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -314,7 +314,8 @@ Before you can create your logic app, create a local project so that you can man
314314
> [!NOTE]
315315
> You might get an error named **azureLogicAppsStandard.createNewProject** with the error message,
316316
> **Unable to write to Workspace Settings because azureFunctions.suppressProject is not a registered configuration**.
317-
> If you do, try installing the [Azure Functions extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions), either directly from the Visual Studio Marketplace or from inside Visual Studio Code.
317+
> If you do, try installing the [Azure Functions extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions),
318+
> either directly from the Visual Studio Marketplace or from inside Visual Studio Code.
318319
319320
1. If Visual Studio Code prompts you to open your project in the current Visual Studio Code or in a new Visual Studio Code window, select **Open in current window**. Otherwise, select **Open in new window**.
320321

@@ -328,6 +329,22 @@ Before you can create your logic app, create a local project so that you can man
328329

329330
[!INCLUDE [Visual Studio Code - logic app project structure](../../includes/logic-apps-single-tenant-project-structure-visual-studio-code.md)]
330331

332+
> [!NOTE]
333+
>
334+
> By default, in your **local.settings.json** file, the language worker runtime value for your
335+
> Standard logic app is **`dotnet`**. Previously, **`node`** was the default value. However,
336+
> **`dotnet`** is now the default value for all new and existing deployed Standard logic apps,
337+
> even for apps that had a different value. This change shouldn't affect your workflow's runtime,
338+
> and everything should work the same way as before. For more information, see the
339+
> [**FUNCTIONS_WORKER_RUNTIME** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
340+
>
341+
> The **APP_KIND** app setting for your Standard logic app is set to **workflowApp**, but in some
342+
> scenarios, this app setting is missing, for example, due to automation using Azure Resource Manager
343+
> templates or other scenarios where the setting isn't included. If certain actions don't work,
344+
> such as the **Execute JavaScript Code** action or the workflow stops working, check that the
345+
> **APP_KIND** app setting exists and is set to to **workflowApp**. For more information, see the
346+
> [**APP_KIND** app setting](edit-app-settings-host-settings.md#reference-local-settings-json).
347+
331348
<a name="convert-project-nuget"></a>
332349

333350
## Convert your project to NuGet package-based (.NET)

‎articles/logic-apps/edit-app-settings-host-settings.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@ App settings in Azure Logic Apps work similarly to app settings in Azure Functio
5454

5555
| Setting | Default value | Description |
5656
|---------|---------------|-------------|
57+
| `APP_KIND` | `workflowApp` | Sets the app type for the Azure resource. |
5758
| `AzureWebJobsStorage` | None | Sets the connection string for an Azure storage account. For more information, see [AzureWebJobsStorage](../azure-functions/functions-app-settings.md#azurewebjobsstorage) |
5859
| `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). |
5960
| `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. |

0 commit comments

Comments
 (0)