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 72cad7016da211eca04e928ce85436d4e79daa43
Author: Andrea Cosentino <[email protected]>
AuthorDate: Wed Jul 22 11:15:38 2020 +0200

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

diff --git a/docs/components/modules/ROOT/pages/aws2-iam-component.adoc 
b/docs/components/modules/ROOT/pages/aws2-iam-component.adoc
index fa05ca1..ed3d8b6 100644
--- a/docs/components/modules/ROOT/pages/aws2-iam-component.adoc
+++ b/docs/components/modules/ROOT/pages/aws2-iam-component.adoc
@@ -43,13 +43,14 @@ You can append query options to the URI in the following 
format,
 
 
 // component options: START
-The AWS 2 Identity and Access Management (IAM) component supports 13 options, 
which are listed below.
+The AWS 2 Identity and Access Management (IAM) component supports 14 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
 | *configuration* (producer) | Component configuration |  | IAM2Configuration
 | *iamClient* (producer) | To use a existing configured AWS IAM as client |  | 
IamClient
 | *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 [...]
@@ -88,12 +89,13 @@ with the following path and query parameters:
 |===
 
 
-=== Query Parameters (13 parameters):
+=== Query Parameters (14 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
 | *iamClient* (producer) | To use a existing configured AWS IAM as client |  | 
IamClient
 | *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 [...]
 | *operation* (producer) | *Required* The operation to perform. The value can 
be one of: listAccessKeys, createUser, deleteUser, getUser, listUsers, 
createAccessKey, deleteAccessKey, updateAccessKey, createGroup, deleteGroup, 
listGroups, addUserToGroup, removeUserFromGroup |  | IAM2Operations

Reply via email to