Update wiki Home page for ibm-secrets-manager
parent
20a9fbd6e4
commit
7827940ca8
39
Home.md
39
Home.md
@ -1,21 +1,32 @@
|
||||
# Deploy the Project on CamelX Platform
|
||||
# IBM Secrets Manager
|
||||
|
||||
Deploy on CamelX Platform in three steps
|
||||
Manage secrets in IBM Secrets Manager 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 | `ibm-secrets-manager` |
|
||||
| Support Level | Preview |
|
||||
| Labels | cloud,cloud |
|
||||
| Version | 4.20.0 (CEQ 3.36.0) |
|
||||
|
||||
## 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.quarkus</groupId>
|
||||
<artifactId>camel-quarkus-ibm-secrets-manager</artifactId>
|
||||
<version>4.20.0 (CEQ 3.36.0)</version>
|
||||
</dependency>
|
||||
```
|
||||
|
||||
## Step 3: Expose
|
||||
Enable **"Expose"**
|
||||
## Endpoint Properties
|
||||
|
||||
Choose an **API Gateway** (Internal, Public, etc.)
|
||||
| Name | Type | Required | Default | Description |
|
||||
|------|------|----------|---------|-------------|
|
||||
| `label` | string | ✓ | | Logical name |
|
||||
| `operation` | enum | | | Operation to be performed |
|
||||
| `serviceUrl` | string | | | Service URL for IBM Secrets Manager |
|
||||
| `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 | | | IBM Cloud API Token for IBM Secrets Manager |
|
||||
|
||||
Loading…
Reference in New Issue
Block a user