From 2ce1d8d6556f072191ea29e53f142f8ce8fea7a8 Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:38:19 +0000
Subject: [PATCH] Update wiki Home page for google-functions

---
 Home.md | 42 ++++++++++++++++++++++++++++--------------
 1 file changed, 28 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..179d7c8 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,35 @@
-# Deploy the Project on CamelX Platform
+# Google Cloud Functions
 
-Deploy on CamelX Platform in three steps
+Manage and invoke Google Cloud Functions
 
-## 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 | `google-functions` |
+| 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-google-functions</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 |
+|------|------|----------|---------|-------------|
+| `functionName` | string | ✓ |  | The user-defined name of the function |
+| `serviceAccountKey` | string |  |  | Service account key to authenticate an application as a service account |
+| `location` | string |  |  | The Google Cloud Location (Region) where the Function is located |
+| `operation` | object |  |  | The operation to perform on the producer. |
+| `pojoRequest` | boolean |  | `false` | Specifies if the request is a pojo request |
+| `project` | string |  |  | The Google Cloud Project name where the Function is located |
+| `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. |
+| `client` | object |  |  | The client to use during service invocation. |