This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 60a289b2a03ee25354916bd90ae60af5087522a6
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Mon Nov 16 17:49:56 2020 +0100
CAMEL-15836 - Camel-AWS2-Kinesis: enable autowire on the Kinesis client,
added a note to migration guide
---
docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc | 3 +++
1 file changed, 3 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc
index c25c7a1..b798a7c 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc
@@ -203,6 +203,9 @@ In this context, it wasn't having any sense to maintain the
autodiscoverClient o
=== Camel-AWS2-Kinesis Autowire support
+The camel-aws2-kinesis has now support for autowiring the amazonKinesisClient
option with KinesisClient instance coming from the registry.
+In this context, it wasn't having any sense to maintain the autodiscoverClient
option, which has been now removed.
+
The camel-aws2-kinesis-firehose has now support for autowiring the
amazonKinesisFirehoseClient option with FirehoseClient instance coming from the
registry.
In this context, it wasn't having any sense to maintain the autodiscoverClient
option, which has been now removed.
