Azure Storage Blob Append Sink
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Adds each message at the end of an append blob in Azure Blob Storage, named after the file header, and creates the blob when it does not exist yet.
Use it to collect log lines, audit records or CSV rows from many messages into one growing blob. To write each message as a blob of its own, use azure-storage-blob-sink.
Input: the body is the data to add: text, bytes or a stream. It is added as it is, so end each line with a line break yourself. Turn structured data such as a Map into JSON text first, for example with json-serialize-action. The file header (or ce-file) is the name of the blob, such as logs/app.log. Without it, each message goes to a new blob with a generated unique name.
Output: the body afterwards is true, and headers such as CamelAzureStorageBlobAppendOffset and CamelAzureStorageBlobCommittedBlockCount describe the append.
Good to know: the container must exist: a missing container fails the message. A name that is already used by a block blob, such as one written by azure-storage-blob-sink, fails the message too.
Configuration Options
The following table summarizes the configuration options available for the azure-storage-blob-append-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
Account Name | Required The name of the storage account, as shown in the Azure portal under Storage accounts. It is the first part of the address of the account, | string | mystorageaccount | ||
Container Name | Required The name of the container in the storage account that holds the append blobs. | string | logs | ||
Access Key | An access key of the storage account, from the Azure portal: the storage account, then Security + networking, then Access keys. Used when | string | |||
Client ID | The application (client) ID of an app registration (service principal) in Microsoft Entra ID that has access to the storage account, from the Overview page of the app registration in the Azure portal. Used with | string | |||
Client Secret | A client secret of the app registration, from the Azure portal: the app registration, then Certificates & secrets. Used with | string | |||
Credential Type | How to log in to the storage account. Enum values: * SHARED_ACCOUNT_KEY * AZURE_IDENTITY * CLIENT_SECRET | string | SHARED_ACCOUNT_KEY | ||
Tenant ID | The directory (tenant) ID of the app registration, from its Overview page in the Azure portal. Used with | string |
Dependencies
At runtime, the azure-storage-blob-append-sink Kamelet relies upon the presence of the following dependencies:
-
camel:azure-storage-blob
-
camel:kamelet
Camel JBang usage
Prerequisites
-
You’ve installed JBang.
-
You have executed the following command:
jbang app install camel@apache/camel Supposing you have a file named route.yaml with this content:
- route:
from:
uri: "kamelet:timer-source"
parameters:
period: 10000
message: 'test'
steps:
- to:
uri: "kamelet:azure-storage-blob-append-sink" You can now run it directly through the following command
camel run route.yaml Azure Storage Blob Append Sink Kamelet Description
Authentication methods
In this Kamelet, you can use these Azure authentication methods:
-
Azure Identity mechanism:
AZURE_IDENTITY -
Plain Shared Account Key:
SHARED_ACCOUNT_KEY
The order of evaluation for AZURE_IDENTITY is the following:
-
Enviroment
-
Workload Identity
-
Managed Identity
-
Azure Developer CLI
-
IntelliJ
-
Azure CLI
-
Azure Powershell
To log in as an app registration (a service principal), set credentialType to AZURE_IDENTITY and provide clientId, clientSecret, and tenantId: when all three are set, they are used instead of the order above. CLIENT_SECRET does not use these three properties.
For more information, see the Azure Identity documentation