Deploying a Flogo App to Microsoft Azure Functions

After you have designed a Flogo app or imported an existing one, you can deploy it to Microsoft Azure Functions as a custom Docker container. You can do this by using the Azure CLI.

Creating the Azure Function App from the Azure CLI

• Visual Studio Code: For more information, see Visual Studio Code.
• Azure Functions extension for Visual Studio Code: For more information, see Visual Studio Code - Azure Functions.
• Azure Functions Core Tools (version 3.x or higher): For more information, see Local Azure Functions.

Procedure
1. Create a new directory (for example, flogo-func-project) and open it.
Copy

cd flogo-func-project

2. Create a new function project using the following command:

Copy

func init --worker-runtime custom --docker

The --docker option generates a Dockerfile for the project.

3. Add a new function from a template using the following command:

Copy

func new --name <your-app-name> --template "HTTP trigger"

Here:

--name argument is the unique name of your function

--template argument specifies the template based on which the function is created

Example:

Copy

func new --name hello-world --template "HTTP trigger"

4. Download or build the executable for your HTTP trigger app and copy it into the directory you created earlier.

For example, copy hello-world.json to the flogo-func-project directory.

5. If it is not an executable file, make it executable by running the following command:

Copy

chmod +x <executable-filename>

6. Add the following script to your project folder with the name start.sh:

   Copy

   start.sh

   #!/usr/bin/env sh
   echo "Starting function..."
   PORT=${FUNCTIONS_CUSTOMHANDLER_PORT} ./hello-world-linux_amd64

7. Make it executable by running the following command:
Copy

chmod +x start.sh

8. To update the default app prefix from api to your prefix, edit the function.json file. For example, you can change the prefix to hello-world.

Copy

function.json

{
    "bindings": [
        {
            "authLevel": "anonymous",
            "type": "httpTrigger",
            "direction": "in",
            "name": "req",
            "methods": ["get", "post"],
            "route": "books/{bookID}"
        },
        {
            "type": "http",
            "direction": "out",
            "name": "res"
        }
    ]
}

9. To add customHeaders in the extensions, edit the host.json file:
Copy

host.json

{
    "version": "2.0",
    "logging": {
        "applicationInsights": {
            "samplingSettings": {
                "isEnabled": true,
                "excludedTypes": "Request"
            }
        }
    },
    "extensionBundle": {
        "id": "Microsoft.Azure.Functions.ExtensionBundle",
        "version": "[2.*, 3.0.0)"
    },
    "customHandler": {
        "description": {
            "defaultExecutablePath": "start.sh",
            "workingDirectory": "",
            "arguments": []
        },
        "enableForwardingHttpRequest": true
    },
    "extensions": {
        "http": {
            "routePrefix": ""
        }
    }
}

10. To change the path, edit the Dockerfile:
Copy

Dockerfile

FROM mcr.microsoft.com/azure-functions/dotnet:3.0-appservice 
ENV AzureWebJobsScriptRoot=/home/site/wwwroot \
AzureFunctionsJobHost__Logging__Console__IsEnabled=true
COPY . /home/site/wwwroot

Your folder structure should now look similar to the following:

.
├── Dockerfile
├── hello-world-app
│   └── function.json
├── hello-world-rest-trigger-linux_amd64
├── host.json
├── local.settings.json
└── start.sh

11. Test your app locally by running the following command:
    

    Copy

    func start

    The output returns an URL for the app.

12. Test whether the app works by navigating to the URL provided in the output. For example:

    Copy

    http://localhost:7071/hello-world

13. Publish your app to Microsoft Azure. For more information, see Publish the project to Azure.