Architecture

Diagram

%%{init: {'securityLevel': 'loose', 'theme':'base'}}%%
graph TD
    K["Controller Entry <br/>(controller)"]
    A["Parse CLI <br/>(lama2cmd)"]
    B["Parser <br/>(parser)"] 
    D["Request Executor <br/>(cmdexec)"]
    E["Output Format Manager <br/>(outputmanager)"]
    F["Error Reporting (TODO)"]
    G["Load input & environment vars <br/>(preprocess)"]
    H["Request Command Generator <br/>(cmdgen)"]
    I["Lama2 Prettifier"]
    J["Data Importer (importer)"]
    L["Iterate over blocks <br/>(controller)"]
    M["Init Javascript processor VM <br/>(cmdexec)"]
    N["Execute JS <br/>(cmdexec)"]
    P["Variable expansion (JS + env) <br/>(preprocess)"]
    A --> G
    A --> J
    G --> B
    H --> D
    K --> A
    B --> M
    M --> L
    L --> |Requestor| P
    L --> |Processor| N
    N --> E
    D --> E
    B --> F
    A --> I
    P --> H
    L --> L

Description

From a high level, how does it work now?

1. Read API file
2. Create a tree-like structure based on *gabs.Container
3. Initialize Javascript VM for executing JS blocks
4. For each block
   1. If block is JS Processor block
      1. Execute JS code in VM
   2. Else if block is Requestor block
      1. Replace variables with values in the following order
         1. Try fetch variable from Javascript VM
         2. If (1) fails, try fetch Local env variable from l2.env
         3. Try fetch root env variable from l2config.env
      2. Use the processed elements to create an httpie-go request
      3. Fetch response
5. If necessary, write the last transaction to .json file