Bootstrap CLI¶
An important aspect of Wishbone is the ability to bootstrap a server on CLI.
To bootstrap you need the following items:
Behind the scenes, the Wishbone bootstrap process automatically makes a couple of configurations:
- All the
_metrics
queues of all modules are connected awishbone.module.flow.funnel
instance called_metrics
from where the user can optionally connect modules for further metric processing. - All the
_logs
queues of all modules are connected awishbone.module.flow.funnel
instance called_logs
. The_logs
module instance is then connected to awishbone.module.flow.queueselect
instance called_logs_filter
in order to filter out the logs according to the--log_level
value. - If the
Wishbone
server is started with--fork
then_logs_filter.pass
is connected to awishbone.module.output.syslog
instance called_logs_syslog
which has the effect all modules logs are written to syslog. - If the
Wishbone
server is started without--fork
then_logs_filter.pass
is connected to awishbone.module.output.stdout
instances called_logs_stdout
which has the effect all modules logs are written to stdout.
The following bootstrap file:
modules:
input:
module: wishbone.module.input.generator
arguments:
payload: hello world
output:
module: wishbone.module.output.stdout
routingtable:
- input.outbox -> output.inbox
Generates following setup when run in foreground:
This includes the user defined input.outbox -> output.inbox
connections
including the auto-generated metrics and logs modules.