Openshift Build Config
Since Camel 2.17
Only producer is supported
The OpenShift Build Config component is one of Kubernetes Components which provides a producer to execute Openshift Build Configs operations.
Component Options
The Openshift Build Config component supports 2 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
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 starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
basicPropertyBinding (advanced) |
Deprecated Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
boolean |
Endpoint Options
The Openshift Build Config endpoint is configured using URI syntax:
openshift-build-configs:masterUrl
with the following path and query parameters:
Path Parameters (1 parameters):
Name | Description | Default | Type |
---|---|---|---|
masterUrl |
Required Kubernetes Master url |
String |
Query Parameters (22 parameters):
Name | Description | Default | Type |
---|---|---|---|
apiVersion (producer) |
The Kubernetes API Version to use |
String |
|
dnsDomain (producer) |
The dns domain, used for ServiceCall EIP |
String |
|
kubernetesClient (producer) |
Default KubernetesClient to use if provided |
KubernetesClient |
|
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 starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
operation (producer) |
Producer operation to do on Kubernetes |
String |
|
portName (producer) |
The port name, used for ServiceCall EIP |
String |
|
portProtocol (producer) |
The port protocol, used for ServiceCall EIP |
tcp |
String |
basicPropertyBinding (advanced) |
Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
boolean |
connectionTimeout (advanced) |
Connection timeout in milliseconds to use when making requests to the Kubernetes API server. |
Integer |
|
synchronous (advanced) |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
boolean |
caCertData (security) |
The CA Cert Data |
String |
|
caCertFile (security) |
The CA Cert File |
String |
|
clientCertData (security) |
The Client Cert Data |
String |
|
clientCertFile (security) |
The Client Cert File |
String |
|
clientKeyAlgo (security) |
The Key Algorithm used by the client |
String |
|
clientKeyData (security) |
The Client Key data |
String |
|
clientKeyFile (security) |
The Client Key file |
String |
|
clientKeyPassphrase (security) |
The Client Key Passphrase |
String |
|
oauthToken (security) |
The Auth Token |
String |
|
password (security) |
Password to connect to Kubernetes |
String |
|
trustCerts (security) |
Define if the certs we used are trusted anyway or not |
Boolean |
|
username (security) |
Username to connect to Kubernetes |
String |
Openshift Build Configs Producer Examples
-
listBuilds: this operation list the Build Configs on an Openshift cluster
from("direct:list").
toF("openshift-build-configs:///?kubernetesClient=#kubernetesClient&operation=listBuildConfigs").
to("mock:result");
This operation return a List of Builds from your Openshift cluster
-
listBuildsByLabels: this operation list the build configs by labels on an Openshift cluster
from("direct:listByLabels").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
Map<String, String> labels = new HashMap<>();
labels.put("key1", "value1");
labels.put("key2", "value2");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_BUILD_CONFIGS_LABELS, labels);
}
});
toF("openshift-build-configs:///?kubernetesClient=#kubernetesClient&operation=listBuildConfigsByLabels").
to("mock:result");
This operation return a List of Build configs from your cluster, using a label selector (with key1 and key2, with value value1 and value2)
Spring Boot Auto-Configuration
When using kubernetes with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-kubernetes-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 74 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
camel.component.kubernetes-config-maps.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-config-maps.enabled |
Whether to enable auto configuration of the kubernetes-config-maps component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-config-maps.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-custom-resources.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-custom-resources.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.kubernetes-custom-resources.enabled |
Whether to enable auto configuration of the kubernetes-custom-resources component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-custom-resources.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-deployments.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-deployments.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.kubernetes-deployments.enabled |
Whether to enable auto configuration of the kubernetes-deployments component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-deployments.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-hpa.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-hpa.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.kubernetes-hpa.enabled |
Whether to enable auto configuration of the kubernetes-hpa component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-hpa.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-job.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-job.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.kubernetes-job.enabled |
Whether to enable auto configuration of the kubernetes-job component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-job.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-namespaces.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-namespaces.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.kubernetes-namespaces.enabled |
Whether to enable auto configuration of the kubernetes-namespaces component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-namespaces.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-nodes.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-nodes.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.kubernetes-nodes.enabled |
Whether to enable auto configuration of the kubernetes-nodes component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-nodes.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-persistent-volumes-claims.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-persistent-volumes-claims.enabled |
Whether to enable auto configuration of the kubernetes-persistent-volumes-claims component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-persistent-volumes-claims.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-persistent-volumes.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-persistent-volumes.enabled |
Whether to enable auto configuration of the kubernetes-persistent-volumes component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-persistent-volumes.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-pods.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-pods.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.kubernetes-pods.enabled |
Whether to enable auto configuration of the kubernetes-pods component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-pods.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-replication-controllers.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-replication-controllers.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.kubernetes-replication-controllers.enabled |
Whether to enable auto configuration of the kubernetes-replication-controllers component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-replication-controllers.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-resources-quota.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-resources-quota.enabled |
Whether to enable auto configuration of the kubernetes-resources-quota component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-resources-quota.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-secrets.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-secrets.enabled |
Whether to enable auto configuration of the kubernetes-secrets component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-secrets.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-service-accounts.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-service-accounts.enabled |
Whether to enable auto configuration of the kubernetes-service-accounts component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-service-accounts.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-services.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-services.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.kubernetes-services.enabled |
Whether to enable auto configuration of the kubernetes-services component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-services.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes.cluster.service.attributes |
Custom service attributes. |
Map |
|
camel.component.kubernetes.cluster.service.cluster-labels |
Set the labels used to identify the pods composing the cluster. |
Map |
|
camel.component.kubernetes.cluster.service.config-map-name |
Set the name of the ConfigMap used to do optimistic locking (defaults to 'leaders'). |
String |
|
camel.component.kubernetes.cluster.service.connection-timeout-millis |
Connection timeout in milliseconds to use when making requests to the Kubernetes API server. |
Integer |
|
camel.component.kubernetes.cluster.service.enabled |
Sets if the Kubernetes cluster service should be enabled or not, default is false. |
false |
Boolean |
camel.component.kubernetes.cluster.service.id |
Cluster Service ID |
String |
|
camel.component.kubernetes.cluster.service.jitter-factor |
A jitter factor to apply in order to prevent all pods to call Kubernetes APIs in the same instant. |
Double |
|
camel.component.kubernetes.cluster.service.kubernetes-namespace |
Set the name of the Kubernetes namespace containing the pods and the configmap (autodetected by default) |
String |
|
camel.component.kubernetes.cluster.service.lease-duration-millis |
The default duration of the lease for the current leader. |
Long |
|
camel.component.kubernetes.cluster.service.master-url |
Set the URL of the Kubernetes master (read from Kubernetes client properties by default). |
String |
|
camel.component.kubernetes.cluster.service.order |
Service lookup order/priority. |
Integer |
|
camel.component.kubernetes.cluster.service.pod-name |
Set the name of the current pod (autodetected from container host name by default). |
String |
|
camel.component.kubernetes.cluster.service.renew-deadline-millis |
The deadline after which the leader must stop its services because it may have lost the leadership. |
Long |
|
camel.component.kubernetes.cluster.service.retry-period-millis |
The time between two subsequent attempts to check and acquire the leadership. It is randomized using the jitter factor. |
Long |
|
camel.component.openshift-build-configs.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.openshift-build-configs.enabled |
Whether to enable auto configuration of the openshift-build-configs component. This is enabled by default. |
Boolean |
|
camel.component.openshift-build-configs.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.openshift-builds.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.openshift-builds.enabled |
Whether to enable auto configuration of the openshift-builds component. This is enabled by default. |
Boolean |
|
camel.component.openshift-builds.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 processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |