Optimizing and Debugging the Flogo App Executable

You can use the Flogo app build configuration file to include only the necessary dependencies during the build process, which reduces download size and build time. You can use the debug logs to identify the Go proxy used to download the dependencies, the approximate download speed, and the time taken for the downloads.

  1. Create a file named flogo-build-config.yaml.

  2. Add the following content to the file to specify integrations and build log settings:

    # jaegar and opentelemetry integrations are enabled in this example. You can uncomment the integrations as per the need
    configuration:
    integrations:
    # - awsxray
    # - awsparamstore
    # - awsappconfig
    # - azurekeyvault
    # - consul
    - jaegar
    # - k8ssecret
    - opentelemetry
    # - prometheus
    generateBuildLog: false

    The Flogo runtime uses this file to download the necessary dependencies or integrations. If all integrations are disabled, the runtime downloads all dependencies.

  3. Configure the file location using one of the following methods:

    1. Home Directory: Add the flogo-build-config.yaml file to your user home directory (for example, Windows C:\Users\<your-user>).

    2. Environment Variable: Set the FLOGO_APP_BUILD_CONFIG environment variable to the file path.

    Note: The file name must match flogo-build-config.yaml if it is added in the home directory. The file provided by the environment variable takes precedence.

  4. To enable build debug logs, set FLOGO_APP_BUILD_LOG=true in the system environment variables and restart Visual Studio Code. Or, you can use the flogo-build-config file and set generateBuildLog:true.

When enabled, a log file named <app-executable>-build.log is generated in the bin folder for every application build.