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-spring-boot.git


The following commit(s) were added to refs/heads/master by this push:
     new c877c6b  [create-pull-request] automated change
c877c6b is described below

commit c877c6ba71dcf53e6384492cfe64843397f12b4d
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Tue Aug 18 01:27:35 2020 +0000

    [create-pull-request] automated change
---
 components-starter/README.adoc                     |  5 ++-
 .../ROOT/pages/azure-eventhubs-starter.adoc        | 52 ++++++++++++++++++++++
 docs/modules/ROOT/pages/list.adoc                  |  5 ++-
 tooling/camel-spring-boot-dependencies/pom.xml     |  5 +++
 4 files changed, 65 insertions(+), 2 deletions(-)

diff --git a/components-starter/README.adoc b/components-starter/README.adoc
index 4597f2e..f8b04fc 100644
--- a/components-starter/README.adoc
+++ b/components-starter/README.adoc
@@ -5,7 +5,7 @@ Apache Camel Spring Boot supports the following Camel artifacts 
as Spring Boot S
 == Camel Components
 
 // components: START
-Number of Camel components: 336 in 269 JAR artifacts (3 deprecated)
+Number of Camel components: 337 in 270 JAR artifacts (3 deprecated)
 
 [width="100%",cols="4,1,5",options="header"]
 |===
@@ -185,6 +185,9 @@ Number of Camel components: 336 in 269 JAR artifacts (3 
deprecated)
 | 
link:https://camel.apache.org/components/latest/aws-translate-component.html[AWS
 Translate] (camel-aws-translate-starter) +
 `aws-translate:label` | 3.0 | Translate texts using AWS Translate.
 
+| 
link:https://camel.apache.org/components/latest/azure-eventhubs-component.html[Azure
 Event Hubs] (camel-azure-eventhubs-starter) +
+`azure-eventhubs:namespace/eventHubName` | 3.5 | The azure-eventhubs component 
that integrates Azure Event Hubs using AMQP protocol. Azure EventHubs is a 
highly scalable publish-subscribe service that can ingest millions of events 
per second and stream them to multiple consumers.
+
 | 
link:https://camel.apache.org/components/latest/azure-storage-blob-component.html[Azure
 Storage Blob Service] (camel-azure-storage-blob-starter) +
 `azure-storage-blob:containerName` | 3.3 | Store and retrieve blobs from Azure 
Storage Blob Service using SDK v12.
 
diff --git a/docs/modules/ROOT/pages/azure-eventhubs-starter.adoc 
b/docs/modules/ROOT/pages/azure-eventhubs-starter.adoc
new file mode 100644
index 0000000..db51525
--- /dev/null
+++ b/docs/modules/ROOT/pages/azure-eventhubs-starter.adoc
@@ -0,0 +1,52 @@
+// spring-boot-auto-configure options: START
+:page-partial:
+:doctitle: Camel Spring Boot Starter for azure-eventhubs
+
+== Spring Boot Auto-Configuration
+
+When using azure-eventhubs with Spring Boot make sure to use the following 
Maven dependency to have support for auto configuration:
+
+[source,xml]
+----
+<dependency>
+  <groupId>org.apache.camel.springboot</groupId>
+  <artifactId>camel-azure-eventhubs-starter</artifactId>
+  <version>x.x.x</version>
+  <!-- use the same version as your Camel core version -->
+</dependency>
+----
+
+
+The component supports 22 options, which are listed below.
+
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *camel.component.azure-eventhubs.amqp-retry-options* | Sets the retry policy 
for EventHubAsyncClient. If not specified, the default retry options are used. 
The option is a com.azure.core.amqp.AmqpRetryOptions type. |  | String
+| *camel.component.azure-eventhubs.amqp-transport-type* | Sets the transport 
type by which all the communication with Azure Event Hubs occurs. Default value 
is AmqpTransportType#AMQP. |  | AmqpTransportType
+| *camel.component.azure-eventhubs.auto-discover-client* | Setting the 
autoDiscoverClient mechanism, if true, the component will look for a client 
instance in the registry automatically otherwise it will skip that checking. | 
true | Boolean
+| *camel.component.azure-eventhubs.basic-property-binding* | Whether the 
component should use basic property binding (Camel 2.x) or the newer property 
binding with additional capabilities | false | Boolean
+| *camel.component.azure-eventhubs.blob-access-key* | In case you chose the 
default BlobCheckpointStore, this sets access key for the associated azure 
account name to be used for authentication with azure blob services |  | String
+| *camel.component.azure-eventhubs.blob-account-name* | In case you chose the 
default BlobCheckpointStore, this sets Azure account name to be used for 
authentication with azure blob services. |  | String
+| *camel.component.azure-eventhubs.blob-container-name* | In case you chose 
the default BlobCheckpointStore, this sets the blob container that shall be 
used by the BlobCheckpointStore to store the checkpoint offsets |  | String
+| *camel.component.azure-eventhubs.blob-storage-shared-key-credential* | In 
case you chose the default BlobCheckpointStore, StorageSharedKeyCredential can 
be injected to create the azure client, this holds the important authentication 
information. The option is a 
com.azure.storage.common.StorageSharedKeyCredential type. |  | String
+| *camel.component.azure-eventhubs.bridge-error-handler* | Allows for bridging 
the consumer to the Camel routing Error Handler, which mean any exceptions 
occurred while the consumer is trying to pickup incoming messages, or the 
likes, will now be processed as a message and handled by the routing Error 
Handler. By default the consumer will use the 
org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be 
logged at WARN or ERROR level and ignored. | false | Boolean
+| *camel.component.azure-eventhubs.checkpoint-store* | Sets the 
CheckpointStore the EventProcessorClient will use for storing partition 
ownership and checkpoint information. Users can, optionally, provide their own 
implementation of CheckpointStore which will store ownership and checkpoint 
information. By default it set to use 
com.azure.messaging.eventhubs.checkpointstore.blob.BlobCheckpointStore which 
stores all checkpoint offsets into Azure Blob Storage. The option is a 
com.azure.messa [...]
+| *camel.component.azure-eventhubs.configuration* | The component 
configurations. The option is a 
org.apache.camel.component.azure.eventhubs.EventHubsConfiguration type. |  | 
String
+| *camel.component.azure-eventhubs.connection-string* | Instead of supplying 
namespace, sharedAccessKey, sharedAccessName ... etc, you can just supply the 
connection string for your eventHub. The connection string for EventHubs 
already include all the necessary information to connection to your EventHub. 
To learn on how to generate the connection string, take a look at this 
documentation: 
\https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string
 |  | String
+| *camel.component.azure-eventhubs.consumer-group-name* | Sets the name of the 
consumer group this consumer is associated with. Events are read in the context 
of this group. The name of the consumer group that is created by default is 
{link #DEFAULT_CONSUMER_GROUP_NAME \$Default}. | $Default | String
+| *camel.component.azure-eventhubs.enabled* | Whether to enable auto 
configuration of the azure-eventhubs component. This is enabled by default. |  
| Boolean
+| *camel.component.azure-eventhubs.event-position* | Sets the map containing 
the event position to use for each partition if a checkpoint for the partition 
does not exist in CheckpointStore. This map is keyed off of the partition id. 
If there is no checkpoint in CheckpointStore and there is no entry in this map, 
the processing of the partition will start from {link EventPosition#latest() 
latest} position. |  | Map
+| *camel.component.azure-eventhubs.lazy-start-producer* | Whether the producer 
should be started lazy (on the first message). By starting lazy you can use 
this to allow CamelContext and routes to startup in situations where a producer 
may otherwise fail during starting and cause the route to fail being started. 
By deferring this startup to be lazy then the startup failure can be handled 
during routing messages via Camel's routing error handlers. Beware that when 
the first message is proc [...]
+| *camel.component.azure-eventhubs.partition-id* | Sets the identifier of the 
Event Hub partition that the {link EventData events} will be sent to. If the 
identifier is not specified, the Event Hubs service will be responsible for 
routing events that are sent to an available partition. |  | String
+| *camel.component.azure-eventhubs.partition-key* | Sets a hashing key to be 
provided for the batch of events, which instructs the Event Hubs service to map 
this key to a specific partition. The selection of a partition is stable for a 
given partition hashing key. Should any other batches of events be sent using 
the same exact partition hashing key, the Event Hubs service will route them 
all to the same partition. This should be specified only when there is a need 
to group events by part [...]
+| *camel.component.azure-eventhubs.prefetch-count* | Sets the count used by 
the receiver to control the number of events the Event Hub consumer will 
actively receive and queue locally without regard to whether a receive 
operation is currently active. | 500 | Integer
+| *camel.component.azure-eventhubs.producer-async-client* | Sets the 
EventHubProducerAsyncClient.An asynchronous producer responsible for 
transmitting EventData to a specific Event Hub, grouped together in batches. 
Depending on the {link CreateBatchOptions options} specified when creating an 
\{linkEventDataBatch\}, the events may be automatically routed to an available 
partition or specific to a partition. Use by this component to produce the data 
in camel producer. The option is a com.a [...]
+| *camel.component.azure-eventhubs.shared-access-key* | The generated value 
for the SharedAccessName |  | String
+| *camel.component.azure-eventhubs.shared-access-name* | The name you chose 
for your EventHubs SAS keys |  | String
+|===
+
+
+// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/list.adoc 
b/docs/modules/ROOT/pages/list.adoc
index 4597f2e..f8b04fc 100644
--- a/docs/modules/ROOT/pages/list.adoc
+++ b/docs/modules/ROOT/pages/list.adoc
@@ -5,7 +5,7 @@ Apache Camel Spring Boot supports the following Camel artifacts 
as Spring Boot S
 == Camel Components
 
 // components: START
-Number of Camel components: 336 in 269 JAR artifacts (3 deprecated)
+Number of Camel components: 337 in 270 JAR artifacts (3 deprecated)
 
 [width="100%",cols="4,1,5",options="header"]
 |===
@@ -185,6 +185,9 @@ Number of Camel components: 336 in 269 JAR artifacts (3 
deprecated)
 | 
link:https://camel.apache.org/components/latest/aws-translate-component.html[AWS
 Translate] (camel-aws-translate-starter) +
 `aws-translate:label` | 3.0 | Translate texts using AWS Translate.
 
+| 
link:https://camel.apache.org/components/latest/azure-eventhubs-component.html[Azure
 Event Hubs] (camel-azure-eventhubs-starter) +
+`azure-eventhubs:namespace/eventHubName` | 3.5 | The azure-eventhubs component 
that integrates Azure Event Hubs using AMQP protocol. Azure EventHubs is a 
highly scalable publish-subscribe service that can ingest millions of events 
per second and stream them to multiple consumers.
+
 | 
link:https://camel.apache.org/components/latest/azure-storage-blob-component.html[Azure
 Storage Blob Service] (camel-azure-storage-blob-starter) +
 `azure-storage-blob:containerName` | 3.3 | Store and retrieve blobs from Azure 
Storage Blob Service using SDK v12.
 
diff --git a/tooling/camel-spring-boot-dependencies/pom.xml 
b/tooling/camel-spring-boot-dependencies/pom.xml
index 4136f36..dc152d7 100644
--- a/tooling/camel-spring-boot-dependencies/pom.xml
+++ b/tooling/camel-spring-boot-dependencies/pom.xml
@@ -2214,6 +2214,11 @@
       </dependency>
       <dependency>
         <groupId>org.apache.camel</groupId>
+        <artifactId>camel-azure-eventhubs</artifactId>
+        <version>3.5.0-SNAPSHOT</version>
+      </dependency>
+      <dependency>
+        <groupId>org.apache.camel</groupId>
         <artifactId>camel-azure-storage-blob</artifactId>
         <version>3.5.0-SNAPSHOT</version>
       </dependency>

Reply via email to