generated from camel.apache.org/component
2
Home
gitea_admin edited this page 2026-03-11 14:38:36 +00:00
Table of Contents
Hashicorp Vault
Manage secrets in Hashicorp Vault Service
Metadata
| Property | Value |
|---|---|
| Scheme | hashicorp-vault |
| Support Level | Stable |
| Labels | cloud,cloud |
| Version | 4.10.2 |
Maven Dependency
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-hashicorp-vault</artifactId>
<version>4.10.2</version>
</dependency>
Endpoint Properties
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
secretsEngine |
string | Vault Name to be used | ||
cloud |
boolean | false |
Determine if the Hashicorp Vault is deployed on Hashicorp Cloud or not | |
host |
string | Hashicorp Vault instance host to be used | ||
namespace |
string | If the Hashicorp Vault instance is deployed on Hashicorp Cloud, this field will determine the namespace | ||
operation |
object | Operation to be performed | ||
port |
string | 8200 |
Hashicorp Vault instance port to be used | |
scheme |
string | https |
Hashicorp Vault instance scheme to be used | |
secretPath |
string | Hashicorp Vault instance secret Path to be used | ||
vaultTemplate |
object | Instance of Vault template | ||
lazyStartProducer |
boolean | false |
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. | |
token |
string | Token to be used |