Using the AppConfig

Below is a high-level work flow for using AWS Systems Manager AppConfig with your Flogo app.

Before you beginThis document assumes that you have an AWS account, have access to the AWS Systems Manager, and know how to use the AWS Systems Manager AppConfig. Refer to the AWS documentation for the information on the AWS Systems Manager AppConfig.

Overview

  1. Build an app executable that has the app properties already configured in Flogo. For more information on building an app executable, see Building an App Executable.

    In case of TCI, for a new app, you need to set the engine variables for the Flogo app before pushing it to TCI. For an existing app you can configure the engine variables and push the updates to the app in the TCI. To configure the engine variables, refer to Configure App Variables.

  2. Configure AWS AppConfig to work with your Flogo application. To define the properties in AWS AppConfig:
    1. Create an application in AWS Appconfig to organize and manage configuration data.
    2. Select the environment of the application in the Appconfig same as that of the environment of your Flogo app.
    3. Create a configuration profile.

      A configuration profile enables AWS AppConfig to access your hosted configuration versions in its stored location. You can store configurations in YAML, JSON, or as text documents in the AWS AppConfig hosted configuration store.

      Refer to AWS documentation for detailed procedure to set up the AWS AppConfig.

  3. Configure the app properties that you want to override in the AppConfig. At runtime, the app fetches these values from the AppConfig and uses them to replace the default values that were set in your Flogo app.
  4. Set the value of the parameter FLOGO_APP_PROPS_AWS_APPCONFIG to True to establish the connection between your Flogo app and AWS AppConfig.
Note: If you change the app properties values in AWS AppConfig, then you need to repush the app to TCI or re-execute the app executable.