anchor.diff:      "connector.class": "io.debezium.connector.mysql.MySqlConnector", <2>
       "database.hostname": "192.168.99.100", <3>
       "database.port": "3306", <4>
  -    "database.user": "{prodname}-user", <5>
  -    "database.password": "thePassword", <6>
  +    "database.user": "debezium-user", <5>
  +    "database.password": "debezium-user-pw", <6>
       "database.server.id": "184054", <7>
       "database.server.name": "fullfillment", <8>
       "database.whitelist": "inventory", <9>
  
positive.code: . A list of Kafka brokers that the connector uses to write and recover DDL statements to the database history topic.
  . The name of the database history topic.
  . The flag that specifies if the connector should generate on the schema change topic named `fulfillment` events with DDL changes that can be used by consumers.
  
negative.code: 
  [id="configure-the-mysql-connector_{context}"]
  = Configuring the MySQL connector
  
  ifndef::cdc-product[]
  Typically, you configure the {prodname} MySQL connector in a `.json` file using the configuration properties available for the connector.
  
  .Prerequisites
  * You should have completed the xref:install-the-mysql-connector_{context}[installation process] for the connector.
  
  .Procedure
  
  . Set the `"name"` of the connector in the `.json` file.
  . Set the configuration properties that you require for your {prodname} MySQL connector.
  
  TIP: For a complete list of configuration properties, see xref:mysql-connector-configuration-properties_{context}[MySQL connector configuration properties].
  