Update wiki Home page for hwcloud-functiongraph

Home.md

@@ -1,21 +1,42 @@
-# Deploy the Project on CamelX Platform
+# Huawei FunctionGraph
 
-Deploy on CamelX Platform in three steps
+To call serverless functions on Huawei Cloud
 
-## 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 | `hwcloud-functiongraph` |
+| Support Level | Stable |
+| Labels | cloud,serverless |
+| 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-huaweicloud-functiongraph</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 |
+|------|------|----------|---------|-------------|
+| `operation` | string | ✓ |  | Operation to be performed |
+| `endpoint` | string |  |  | FunctionGraph url. Carries higher precedence than region parameter based client initialization |
+| `functionName` | string |  |  | Name of the function to invoke |
+| `functionPackage` | string |  | `default` | Functions that can be logically grouped together |
+| `projectId` | string | ✓ |  | Cloud project ID |
+| `region` | string | ✓ |  | FunctionGraph service region. This is lower precedence than endpoint based configuration |
+| `serviceKeys` | object |  |  | Configuration object for cloud service authentication |
+| `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. |
+| `proxyHost` | string |  |  | Proxy server ip/hostname |
+| `proxyPassword` | string |  |  | Proxy authentication password |
+| `proxyPort` | integer |  |  | Proxy server port |
+| `proxyUser` | string |  |  | Proxy authentication user |
+| `accessKey` | string | ✓ |  | Access key for the cloud user |
+| `ignoreSslVerification` | boolean |  | `false` | Ignore SSL verification |
+| `secretKey` | string | ✓ |  | Secret key for the cloud user |