Manage custom components

In addition to the standard workflow components—processors, operators, splitters, reducers and remappers—Knowledge Models and custom models, EI-Flow can have an inventory of custom components, developed for specific needs.

Custom components are, in practice, Docker images stored in a registry and thus do not take up "space" and computing resources in EI-Flow until when corresponding blocks are instantiated in a published workflow, which takes place in an EI-Flow runtime, be it the built-in one or an external one.

The inventory of custom components you manage with the EI-Flow designer Web application is a database of relatively small image manifests.

Custom components can be public or project-based.
Public custom components are visible to everyone, while project custom components are visible only to the project owner and any users with whom the project has been shared.
The ability to manage public custom components depends on the user's role, while project custom components, aside from the project owner who has full powers on them, depend on the permissions with which the project was shared.
The main page for viewing and managing public custom components is Custom components, while project custom components are viewed and managed in the Assets tab of the project workspace.

The following articles describe all the procedures for managing the manifests of custom components.