Support for Logic App (Standard)

[ronaldbosma]

Hi.

I'm considering contributing to azd to add support for Logic App (Standard), which would address #812. Before I get started, I wanted to check whether the approach I have in mind makes sense.

Currently, when deploying to a Logic App (Standard), you need to configure js as the language. This ensures the assets are zipped and deployed to the Logic App by configuring function as the host. However, this introduces an unnecessary dependency on Node.

A Logic App can also include a custom code project with custom functions. The project can target either .NET Framework or .NET 8 and needs to be built before it is packaged into the Logic App zip file. I’m currently using a prepackage hook for this. For example:

services:
  logicApp:
    project: ./src/logicApp
    dist: Workflows
    host: function
    language: js
    hooks:
      prepackage:
        shell: pwsh
        run: ../../hooks/prepackage-logicapp-build-functions-project.ps1
        interactive: true

It would be great to have native support for Logic App (Standard) projects so that the dependency on Node can be removed, as well as the need for a prepackage hook when a custom code project is included.

Using function as the host makes sense to me, since Logic Apps use the Azure Functions runtime under the hood. Therefore, introducing a new language option seems like the appropriate approach.

For example, consider the following project structure where the Logic App includes a custom code project:

└── src
    └── logicApp
        ├── Functions
        │   ├── MyFunctions.cs
        │   ├── Functions.csproj
        │   └── ...
        └── Workflows
            ├── my-workflow-1
            │   └── workflow.json
            ├── my-workflow-2
            │   └── workflow.json
            └── ...

You could then specify the following in azure.yaml:

services:
  logicApp:
    project: ./src/logicApp
    dist: Workflows
    host: function
    language: workflow
    customCodeProject: Functions

The workflow language (or another suitable name) would indicate that this is a Logic App project containing workflows.

The customCodeProject property would be optional and would indicate that a custom code project is included and needs to be built first.

[vhvb1989]

@rajeshkamal5050 @kristenwomack