Configuring Extensions

To configure an extension:

Note: This procedure assumes that you have the unzipped folder of the .zip extension file available.

Note: Ensure that the go.mod file is present in the unzipped folder or else it generates an error.

    Procedure
  1. In File Explorer, create a folder under your workspace directory.
  2. Add the unzipped version of your extensions file to the newly created folder.
  3. In Visual Studio Code, navigate to View > Command Palette, search Open Users Settings, expand Extensions, and select Flogo.
  4. Specify the path of your extensions folder in the Extension:Local field.
  5. Refresh Visual Studio Code for the changes to be reflected.

Note: Use the path of a local directory instead of a shared location path. Entering a shared location might not work.

ResultThe extension is now available for you to use.

Activity extensions are available in the default category, functional extensions are available in the mapper functions, and trigger extensions are available in the trigger list.

Go Mod Compatibility

For custom extensions to run on Visual Studio Code, extension must be go mod compatible to generate app binary and run successfully.

    Procedure
  1. Add the unzipped version of your extensions file to go/src.
  2. Navigate to go/src/{extension} and open Visual Studio Code .
  3. Run the below commands on the terminal:
    1. go mod init {ref}
      exa. go mod init github.com/TIBCOSoftware/tci-flogo/samples/extensions/AWSSQS/activity/sqssendmessage
    2. go mod tidy
ResultAfter the commands are executed successfully, go.mod and go.sum files are generated.

Download Extensions from Runtime

To download extensions from the TIBCO Cloud™ Integration environment:

    Procedure
  1. Select the icon in Activity Bar.
  2. In the Runtime Explorer, select the desired TIBCO Cloud Integration runtime to download its extensions.
  3. Ensure that you are connected to the runtime.
  4. Right-click and select Download Extensions.

ResultThe extensions are downloaded to your extensions folder as specified in the Extension:Local field.
Note: Only extensions promoted to org are downloaded to the specified folder.