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 48529d18d8bfd03ce3b9701f0732fad2d4d2025d
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Wed Jul 22 08:47:43 2020 +0200

    Regen website docs
---
 docs/components/modules/ROOT/pages/aws-eks-component.adoc | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/components/modules/ROOT/pages/aws-eks-component.adoc 
b/docs/components/modules/ROOT/pages/aws-eks-component.adoc
index 358b7e5..6c15fbd 100644
--- a/docs/components/modules/ROOT/pages/aws-eks-component.adoc
+++ b/docs/components/modules/ROOT/pages/aws-eks-component.adoc
@@ -38,13 +38,14 @@ You can append query options to the URI in the following 
format,
 
 
 // component options: START
-The AWS Elastic Kubernetes Service (EKS) component supports 11 options, which 
are listed below.
+The AWS Elastic Kubernetes Service (EKS) component supports 12 options, which 
are listed below.
 
 
 
 [width="100%",cols="2,5,^1,2",options="header"]
 |===
 | Name | Description | Default | Type
+| *autoDiscoverClient* (common) | 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
 | *accessKey* (producer) | Amazon AWS Access Key |  | String
 | *configuration* (producer) | The component configuration |  | 
EKSConfiguration
 | *eksClient* (producer) | To use a existing configured AWS EKS as client |  | 
AmazonEKS
@@ -81,12 +82,13 @@ with the following path and query parameters:
 |===
 
 
-=== Query Parameters (11 parameters):
+=== Query Parameters (12 parameters):
 
 
 [width="100%",cols="2,5,^1,2",options="header"]
 |===
 | Name | Description | Default | Type
+| *autoDiscoverClient* (common) | 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
 | *accessKey* (producer) | Amazon AWS Access Key |  | String
 | *eksClient* (producer) | To use a existing configured AWS EKS as client |  | 
AmazonEKS
 | *lazyStartProducer* (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 processed 
then creating and [...]

Reply via email to