Davide Bettio

A mqtt_sink block should be added, following features are required: * it should allow custom client_id, username and password * a base topic option should be evaluated

policy might be a better name than action in split_map block, therefore key_policy and fallback_policy should be (discussed and) used instead of `fallback_action` and `fallback_key`.

Our PipelineBuilder language requires expressions such as `${ $.config.foo }` which are not user friendly. See also https://github.com/ispirata/exjsonpath/issues/2 .

Astarte dashboard needs to display the flow status (running, creating, error, etc...), therefore an API should be added.

PipelineBuilder relies on pattern matching and also doesn't make any effort in providing user friendly errors.

An API for flow stats (e.g. messages/s) would provide a useful feedback to users.

Virtual devices should be shut down when they are not used.

A WebSocket sink is required for easy pipeline inspection, debug and data delivery to third party servicies.

We should have either a tracing block, or add a .tracing(true) property to all blocks. Also we must decide if we want to use Logger or an in memory buffer...

Write a tutorial based on generic sensors interfaces with JavaScript snippets from existing examples. The tutorial should show: - Explain employed interfaces and their mappings - How to install required...