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 d4169551942fa1af45281fb58e46eeee28ae47a4
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Fri Jul 24 08:15:45 2020 +0200
Regen website docs
---
docs/components/modules/ROOT/pages/aws2-lambda-component.adoc | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/components/modules/ROOT/pages/aws2-lambda-component.adoc
b/docs/components/modules/ROOT/pages/aws2-lambda-component.adoc
index e16b594..8b6d88e 100644
--- a/docs/components/modules/ROOT/pages/aws2-lambda-component.adoc
+++ b/docs/components/modules/ROOT/pages/aws2-lambda-component.adoc
@@ -45,13 +45,14 @@ You can append query options to the URI in the following
format,
// component options: START
-The AWS 2 Lambda component supports 13 options, which are listed below.
+The AWS 2 Lambda 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 | |
Lambda2Configuration
| *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) | The operation to perform. It can be listFunctions,
getFunction, createFunction, deleteFunction or invokeFunction. The value can be
one of: listFunctions, getFunction, createAlias, deleteAlias, getAlias,
listAliases, createFunction, deleteFunction, invokeFunction, updateFunction,
createEventSourceMapping, deleteEventSourceMapping, listEventSourceMapping,
listTags, tagResource, untagResource, publishVersion, listVersions |
invokeFunction | Lambda2Operations
@@ -90,12 +91,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
| *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) | The operation to perform. It can be listFunctions,
getFunction, createFunction, deleteFunction or invokeFunction. The value can be
one of: listFunctions, getFunction, createAlias, deleteAlias, getAlias,
listAliases, createFunction, deleteFunction, invokeFunction, updateFunction,
createEventSourceMapping, deleteEventSourceMapping, listEventSourceMapping,
listTags, tagResource, untagResource, publishVersion, listVersions |
invokeFunction | Lambda2Operations
| *pojoRequest* (producer) | If we want to use a POJO request as body or not |
false | boolean
