@itentialopensource/adapter-kafkav2 0.6.2 → 0.6.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,4 +1,12 @@
1
1
 
2
+ ## 0.6.3 [05-19-2023]
3
+
4
+ * added support for separate topics files per adapter
5
+
6
+ See merge request itentialopensource/adapters/notification-messaging/adapter-kafkav2!5
7
+
8
+ ---
9
+
2
10
  ## 0.6.2 [05-16-2023]
3
11
 
4
12
  * added support for separate topics files per adapter
package/README.md CHANGED
@@ -282,6 +282,18 @@ The `parseMessage` property allows the user to define how they want the Kafka me
282
282
 
283
283
  `iap_apps_check_interval` (default 30000ms - 30s) allows the user to set the frequency in which to run IAP app healtcheck.
284
284
 
285
+ ## Send message sample payload
286
+
287
+ ```json
288
+ {
289
+ topic: 'topic-name',
290
+ messages: [
291
+ { key: 'key1', value: 'hello world' },
292
+ { key: 'key2', value: 'hey hey!' }
293
+ ],
294
+ }
295
+ ```
296
+
285
297
  ## Testing an Itential Product Adapter
286
298
 
287
299
  Mocha is generally used to test all Itential Product Adapters. There are unit tests as well as integration tests performed. Integration tests can generally be run as standalone using mock data and running the adapter in stub mode, or as integrated. When running integrated, every effort is made to prevent environmental failures, however there is still a possibility.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@itentialopensource/adapter-kafkav2",
3
- "version": "0.6.2",
3
+ "version": "0.6.3",
4
4
  "description": "Itential adapter to connect to kafka",
5
5
  "main": "adapter.js",
6
6
  "wizardVersion": "2.35.0",
Binary file