Update wiki Home page for hwcloud-iam

Home.md

@@ -1,21 +1,40 @@
-# Deploy the Project on CamelX Platform
+# Huawei Identity and Access Management (IAM)
 
-Deploy on CamelX Platform in three steps
+To securely manage users 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-iam` |
+| 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-huaweicloud-iam</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 |
+| `accessKey` | string | ✓ |  | Access key for the cloud user |
+| `groupId` | string |  |  | Group ID to perform operation with |
+| `ignoreSslVerification` | boolean |  | `false` | Ignore SSL verification |
+| `proxyHost` | string |  |  | Proxy server ip/hostname |
+| `proxyPassword` | string |  |  | Proxy authentication password |
+| `proxyPort` | integer |  |  | Proxy server port |
+| `proxyUser` | string |  |  | Proxy authentication user |
+| `region` | string | ✓ |  | IAM service region |
+| `secretKey` | string | ✓ |  | Secret key for the cloud user |
+| `serviceKeys` | object |  |  | Configuration object for cloud service authentication |
+| `userId` | string |  |  | User ID to perform operation with |
+| `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. |