Update wiki Home page for azure-storage-queue-source

gitea_admin 2026-03-11 14:35:14 +00:00
parent 4411acefba
commit 6ef1dfcb2f

38
Home.md

@ -1,21 +1,31 @@
# Deploy the Project on CamelX Platform
# Azure Storage Queue Source
Deploy on CamelX Platform in three steps
Receive events from Azure Storage queues.
## Step 1: Create a release
From the project space, click on **"Create a release"**
One header will be duplicated with different names for clarity at sink level, CamelAzureStorageQueueMessageId will be duplicated into azure.storage.queue.message.id
The new version is automatically available in the list
## Metadata
## Step 2: Deploy
Click on **"Deploy"**
| Property | Value |
|----------|-------|
| Type | source |
| Group | Azure Storage Queue |
| Namespace | Azure |
| Support Level | Stable |
| Provider | Apache Software Foundation |
- **Version:** Select the desired release
- **Environment:** Choose `Development`, `Staging`, or `Production`
- **Configuration:** Select the configuration source
- **Resources:** Set CPU and Memory
## Properties
## Step 3: Expose
Enable **"Expose"**
| Name | Type | Required | Default | Description |
|------|------|----------|---------|-------------|
| `accountName` | string | ✓ | | The Azure Storage Queue account name. |
| `queueName` | string | ✓ | | The Azure Storage Queue container name. |
| `accessKey` | string | ✓ | | The Azure Storage Queue access key. |
| `maxMessages` | integer | | `1` | The maximum number of messages to get. You can specify a value between 1 and 32. The default is 1 (one message). If there are fewer than the maximum number of messages in the queue, then all the messages are returned. |
| `credentialType` | string | | `SHARED_ACCOUNT_KEY` | Determines the credential strategy to adopt. |
Choose an **API Gateway** (Internal, Public, etc.)
## Dependencies
- `camel:azure-storage-queue`
- `camel:kamelet`
- `camel:core`