Azure Storage Blob Data Lake Sink
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Send data to Azure Storage Blob Data Lake.
Configuration Options
The following table summarizes the configuration options available for the azure-storage-datalake-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
Account Name | Required The Azure Storage Blob Data lake account name. | string | |||
Client Id | Required The Azure Storage Blob Data lake client Id. | string | |||
Client Secret | Required The Azure Storage Blob Data lake client secret. | string | |||
File System Name | Required The Azure Storage Blob Data lake File system name. | string | |||
Tenant Id | Required The Azure Storage Blob Data lake tenant id. | string | |||
Credential Type | Determines the credential strategy to adopt. Enum values: * CLIENT_SECRET * SHARED_KEY_CREDENTIAL * AZURE_IDENTITY * AZURE_SAS * SERVICE_CLIENT_INSTANCE | string | CLIENT_SECRET |
Dependencies
At runtime, the azure-storage-datalake-sink
Kamelet relies upon the presence of the following dependencies:
-
camel:azure-storage-datalake
-
camel:kamelet
-
camel:core
-
camel:timer
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-datalake-sink"
You can now run it directly through the following command
camel run route.yaml
Azure Storage Datalake Sink Kamelet Description
Authentication methods
In this Kamelet you have the possibility of using the CLIENT_SECRET, SHARED_KEY_CREDENTIAL, AZURE_IDENTITY, AZURE_SAS and SERVICE_CLIENT_INSTANCE. The default will be CLIENT_SECRET.
The order of evaluation for AZURE_IDENTITY
is the following:
-
Enviroment
-
Workload Identity
-
Managed Identity
-
Azure Developer CLI
-
IntelliJ
-
Azure CLI
-
Azure Powershell
For more information about this you can look at Azure Identity documentation