azure storage queue source Azure Storage Queue Source

Provided by: "Apache Software Foundation"

Support Level for this Kamelet is: "Stable"

Receive events from Azure Storage queues.

One header will be duplicated with different names for clarity at sink level, CamelAzureStorageQueueMessageId will be duplicated into azure.storage.queue.message.id

Configuration Options

The following table summarizes the configuration options available for the azure-storage-queue-source Kamelet:

Property Name Description Type Default Example

accessKey

Access Key

Required The Azure Storage Queue access key.

string

accountName

Account Name

Required The Azure Storage Queue account name.

string

queueName

Queue Name

Required The Azure Storage Queue container name.

string

maxMessages

Maximum Messages

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.

integer

1

Dependencies

At runtime, the azure-storage-queue-source Kamelet relies upon the presence of the following dependencies:

  • camel:azure-storage-queue

  • camel:kamelet

  • github:apache.camel-kamelets:camel-kamelets-utils:3.20.2-SNAPSHOT

  • camel:core

Usage

This section describes how you can use the azure-storage-queue-source.

Knative source

You can use the azure-storage-queue-source Kamelet as a Knative source by binding it to a Knative object.

azure-storage-queue-source-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: azure-storage-queue-source-binding
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: azure-storage-queue-source
    properties:
      accessKey: The Access Key
      accountName: The Account Name
      queueName: The Queue Name
  sink:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel

Prerequisite

You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the azure-storage-queue-source-binding.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the source by using the following command:

    kubectl apply -f azure-storage-queue-source-binding.yaml

Procedure for using the Kamel CLI

Configure and run the source by using the following command:

kamel bind azure-storage-queue-source -p "source.accessKey=The Access Key" -p "source.accountName=The Account Name" -p "source.queueName=The Queue Name" channel:mychannel

This command creates the KameletBinding in the current namespace on the cluster.

Kafka source

You can use the azure-storage-queue-source Kamelet as a Kafka source by binding it to a Kafka topic.

azure-storage-queue-source-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: azure-storage-queue-source-binding
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: azure-storage-queue-source
    properties:
      accessKey: The Access Key
      accountName: The Account Name
      queueName: The Queue Name
  sink:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic

Prerequisites

  • You’ve installed Strimzi.

  • You’ve created a topic named my-topic in the current namespace.

  • You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the azure-storage-queue-source-binding.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the source by using the following command:

    kubectl apply -f azure-storage-queue-source-binding.yaml

Procedure for using the Kamel CLI

Configure and run the source by using the following command:

kamel bind azure-storage-queue-source -p "source.accessKey=The Access Key" -p "source.accountName=The Account Name" -p "source.queueName=The Queue Name" kafka.strimzi.io/v1beta1:KafkaTopic:my-topic

This command creates the KameletBinding in the current namespace on the cluster.