camel.apache.org/google-secret-manager
1
0
Fork 0
generated from camel.apache.org/component
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update wiki Home page for google-secret-manager

gitea_admin 2026-03-11 14:38:26 +00:00
parent bdaea0254e
commit 2582e50318
1 changed files with 26 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
Home.md

@ -1,21 +1,33 @@
# Deploy the Project on CamelX Platform
# Google Secret Manager
Deploy on CamelX Platform in three steps
Manage Google Secret Manager Secrets
## 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 | `google-secret-manager` |
| Support Level | Stable |
| Labels | 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-google-secret-manager</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 |
|------|------|----------|---------|-------------|
| `project` | string | ✓ | | The Google Cloud Project Id name related to the Secret Manager |
| `serviceAccountKey` | string | | | Service account key to authenticate an application as a service account |
| `operation` | object | | | The operation to perform on the producer. |
| `pojoRequest` | boolean | | `false` | Specifies if the request is a pojo request |
| `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. |
| `client` | object | | | The client to use during service invocation. |