Integrates Utilities | Batch Tasks & Debugging | Fluid Attacks Help

Utilities

Introduction

Some of the user’s actions in the platform are not reflected directly when running Integrates locally, and are also not caught by our unit tests. Some examples of this are:
  1. Asynchronous tasks that use batch.
  2. Use external resources to send information to the user via email or message. This includes sending event report emails, downloading executive files, cloning a repository, etc.
To implement a new feature or for debugging purposes, it is important to know the result of such tasks before deploying to production.

Batch asynchronous tasks

There are known asynchronous tasks in the platform, such as cloning roots, doing a rebase in a repository, downloading files, updating group or organization policies, etc. Taking as an example the case of updating the download of an executive report, we will follow the next steps to obtain the PDF file locally.
  1. Select the option to download the report from the platform in localhost:8001, and follow the steps to send a verification code.

    2. exec report

  2. We can see the task is queued in the download center pending execution.

    3. download center

  3. Using the application of NoSQL Workbench, we find the PK ID of the task we just queued with the related action report.

    4. nosql-workbench

  4. Finally, we run the terminal command, and afterwards, we will see the report available in the local platform.
integrates-baych "task_id"

Mailing templates

To check the HTML result when sending email reports, you can:
  1. Adjust the file integrates/back/integrates/mailer/common.py to print the content and allow for processing test groups.
  2. Run the following command to get the output file in VSCode.
integrates-back-cli dev > output.txt
Idea
Tip
Have an idea to simplify our architecture or noticed docs that could use some love? Don't hesitate to open an issue or submit improvements.