Update wiki Home page for hashicorp-vault

gitea_admin 2026-03-11 14:38:36 +00:00
parent 5d2b9d4769
commit 3431a93cac

45
Home.md

@ -1,21 +1,38 @@
# Deploy the Project on CamelX Platform
# Hashicorp Vault
Deploy on CamelX Platform in three steps
Manage secrets in Hashicorp Vault Service
## Step 1: Create a release
From the project space, click on **"Create a release"**
## Metadata
The new version is automatically available in the list
| Property | Value |
|----------|-------|
| Scheme | `hashicorp-vault` |
| Support Level | Stable |
| Labels | cloud,cloud |
| Version | 4.10.2 |
## Step 2: Deploy
Click on **"Deploy"**
## Maven Dependency
- **Version:** Select the desired release
- **Environment:** Choose `Development`, `Staging`, or `Production`
- **Configuration:** Select the configuration source
- **Resources:** Set CPU and Memory
```xml
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-hashicorp-vault</artifactId>
<version>4.10.2</version>
</dependency>
```
## Step 3: Expose
Enable **"Expose"**
## Endpoint Properties
Choose an **API Gateway** (Internal, Public, etc.)
| 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 |