@itentialopensource/adapter-kafkav2 0.15.0 → 0.16.0

package/CHANGELOG.md

@@ -1,4 +1,12 @@
 
+## 0.16.0 [08-23-2023]
+
+* Add logic to clean topics.json from service config
+
+See merge request itentialopensource/adapters/notification-messaging/adapter-kafkav2!11
+
+---
+
 ## 0.15.0 [08-04-2023]
 
 * Add logic to clean topics.json from service config

package/README.md

@@ -351,7 +351,7 @@ Once you have the adapter configured and online in an IAP instance, you can crea
 
 ### Listen to a topic called test-topic and trigger a workflow called test
 
-1. Subscribe to partition 0 of test-topic. Add this to your adapter service config. To see different options of topic properties see PROPERTIES.md
+1. Subscribe to partition 0 of test-topic. Add this to your adapter service config. To see different options of topic properties see Topic Properties.
 
 ```json
 "topics": [
@@ -371,7 +371,7 @@ Once you have the adapter configured and online in an IAP instance, you can crea
 ],
 ```
 
-Note the rabbit key in the config is set to kafka. The adapter will send any message on test-topic-rabbit to a Rabbit queue named kafka. If no rabbit topic is supplied, events will be published to a topic with the same name as the Kafka topic. Also note that the filter array can be left empty to consume all messages on partion 0 of test-topic.
+Note the rabbit key in the config is set to test-topic-rabbit. The adapter will send any message on test-topic to a Rabbit queue named test-topic-rabbit. If no rabbit topic is supplied, events will be published to a topic with the same name as the Kafka topic. Also note that the filter array can be left empty to consume all messages on partion 0 of test-topic.
 
 2. Create an automation in Operations Manager
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@itentialopensource/adapter-kafkav2",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Itential adapter to connect to kafka",
   "main": "adapter.js",
   "wizardVersion": "2.35.0",