FBL specific terms and their definitions.
Any action that one can use in his/her flow is served by Node.js plugin with one or more associated ActionHandler classes.
In the flow file action handler can be referenced via its ID or one of the specified aliases.
Every action has access to the shared object that is called
FBL Context has a following format:
# directory path from where fbl command was executed
# non-secret values storage
# secret values storage
# Summary records that will be printed in the end of execution in a nice ASCII table for user
# Generally used to present tests results or simple tracing reports for user
- title: Count to 5
One or more actions combined into together with defined order of execution.
Dynamic value processing and assignment inside the flow is handled by EJS template.
FBL uses its own concept of referencing paths to read from and write to context fields. And generally have a following look
- Path should always start with
$defines root field. It can be either context or some other target based on the context of usage.
.is used to define relationship between parent and child fields. Where parent is always goes first.
- Path should be read from left to right. Where left represent parent fields and right - their nested ones.
- Path can not reference array elements. Path traveling is only possible to the deepest nested object or first found field with basic type value (number, boolean, string) or array.
Parameters is additional shared object like context, but it is not shared across all actions, but only with ones where parameters are defined and all nested ones (if any). Generally parameters are used to isolate specific values from global scope.
Embedded or external Node.js module that has specific structure and exposes action handlers, template utility functions or custom reporters.