Currently, APIs exposed by Tenzir nodes are not easily accessible in pipelines. The REST API isn't running by default, so from http localhost:5680/v0/pipeline/create <params> read json is not always an option.
The node, however, knows how to run the internal API requests without needing to spawn the API itself. This would allow for adding an api /v0/pipeline/create <params> source operator that does effectively the same, or even convenience operators like create [<options>] <pipeline> that make it easy to use the pipeline manager API from the command line.
There are two main motivations for this:
Testing internal APIs is very cumbersome through the REST API.
Deploying a pipeline cannot currently be done through the command line.
### Definition of Done
- [x] Agree on the desired UX for API access on the command line
- [x] Implement the new operator(s)
Currently, APIs exposed by Tenzir nodes are not easily accessible in pipelines. The REST API isn't running by default, so
from http localhost:5680/v0/pipeline/create <params> read jsonis not always an option.The node, however, knows how to run the internal API requests without needing to spawn the API itself. This would allow for adding an
api /v0/pipeline/create <params>source operator that does effectively the same, or even convenience operators likecreate [<options>] <pipeline>that make it easy to use the pipeline manager API from the command line.There are two main motivations for this: