Update wiki Home page for cyberark-vault

Home.md

@@ -1,21 +1,40 @@
-# Deploy the Project on CamelX Platform
+# CyberArk Vault
 
-Deploy on CamelX Platform in three steps
+Retrieve secrets from CyberArk Conjur Vault.
 
-## 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 | `cyberark-vault` |
+| Support Level | Stable |
+| Labels | cloud,security |
+| 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-cyberark-vault</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 |
+| `account` | string | ✓ |  | The CyberArk Conjur account name |
+| `certificatePath` | string |  |  | Path to the SSL certificate for verification |
+| `conjurClient` | object |  |  | Reference to a ConjurClient instance in the registry |
+| `operation` | enum |  | `getSecret` | The operation to perform. It can be getSecret or createSecret |
+| `secretId` | string |  |  | The secret ID to retrieve from CyberArk Conjur |
+| `url` | string | ✓ |  | The CyberArk Conjur instance URL |
+| `verifySsl` | boolean |  | `true` | Whether to verify SSL certificates when connecting to CyberArk Conjur |
+| `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. |
+| `apiKey` | string |  |  | The API key for authentication with CyberArk Conjur |
+| `authToken` | string |  |  | Pre-authenticated token to use for CyberArk Conjur |
+| `password` | string |  |  | The password for authentication with CyberArk Conjur |
+| `username` | string |  |  | The username for authentication with CyberArk Conjur |