Update wiki Home page for influxdb

Home.md

@@ -1,21 +1,36 @@
-# Deploy the Project on CamelX Platform
+# InfluxDB
 
-Deploy on CamelX Platform in three steps
+Interact with InfluxDB v1, a time series database.
 
-## Step 1: Create a release
+## Metadata
-From the project space, click on **"Create a release"**
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `influxdb` |
+| Support Level | Stable |
+| Labels | database |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
+## Maven Dependency
-Click on **"Deploy"**
 
-- **Version:** Select the desired release
+```xml
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
+<dependency>
-- **Configuration:** Select the configuration source
+    <groupId>org.apache.camel</groupId>
-- **Resources:** Set CPU and Memory
+    <artifactId>camel-influxdb</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
+## Endpoint Properties
-Enable **"Expose"**
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `connectionBean` | string | ✓ |  | Connection to the influx database, of class InfluxDB.class |
+| `autoCreateDatabase` | boolean |  | `false` | Define if we want to auto create the database if it's not present |
+| `batch` | boolean |  | `false` | Define if this operation is a batch operation or not |
+| `checkDatabaseExistence` | boolean |  | `false` | Define if we want to check the database existence while starting the endpoint |
+| `databaseName` | string |  |  | The name of the database where the time series will be stored |
+| `operation` | string |  | `insert` | Define if this operation is an insert or a query |
+| `query` | string |  |  | Define the query in case of operation query |
+| `retentionPolicy` | string |  | `default` | The string that defines the retention policy to the data created by the endpoint |
+| `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. |