anchor.diff:  
   === Transformation configuration
   
  -Before the messages dare delivered to the sink they can run through a sequence of transformation.
  +Before the messages are delivered to the sink, they can run through a sequence of transformations.
   The server supports https://cwiki.apache.org/confluence/display/KAFKA/KIP-66%3A+Single+Message+Transforms+for+Kafka+Connect[single message transformations] defined by Kafka Connect.
   The configuration will need to contain the list of transformations, implementation class for each transformation and configuration options for each of the transformations.
   
  
positive.code: debezium.source.schema.whitelist=inventory
  ----
  
  When the server is started it generates a sequnce of log messages like
  
  ----
  __  ____  __  _____   ___  __ ____  ______ 
  
negative.code: `-- run.sh
  ----
  
  The server is started using `run.sh` script, dependencies are stored in the `lib` directory, and the directory `conf` contains configuration files.
  
  == Configuration
  
  Debezium Server uses https://github.com/eclipse/microprofile-config[MicroProfile Configuration] for configuration.
  This means that the application can be configured from disparate sources like configuration files, environment variables, system properties etc.
  
  The main configuration file is _conf/application.properties_.
  There are multiple sections configured:
  
  * `debezium.source` is for source connector configuration; each instance of Debezium Server runs exactly one connector
  * `debezium.sink` is for the sink system configuration
  * `debezium.format` is for the output serialization format configuration
  * `debezium.transforms` is for the configuration of message transformations
  
  An example configuration file can look like so:
  
  ----
  debezium.sink.type=kinesis
  