Twitter Direct Message Source
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Preview"
Allows to get all direct messages for your Twitter account.
It requires tokens that can be obtained by creating an application in the Twitter developer portal: https://developer.twitter.com/.
Configuration Options
The following table summarizes the configuration options available for the twitter-directmessage-source
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
accessToken * |
Access Token |
The Access Token from the Twitter application in the developer portal |
string |
||
accessTokenSecret * |
Access Token Secret |
The Access Token Secret from the Twitter application in the developer portal |
string |
||
apiKey * |
API Key |
The API Key from the Twitter application in the developer portal |
string |
||
apiKeySecret * |
API Key Secret |
The API Key Secret from the Twitter application in the developer portal |
string |
||
user * |
User |
The user we want to read the direct messages |
string |
|
Fields marked with (*) are mandatory. |
Usage
This section summarizes how the twitter-directmessage-source
can be used in various contexts.
Knative Source
The twitter-directmessage-source
Kamelet can be used as Knative source by binding it to a Knative object.
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: twitter-directmessage-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: twitter-directmessage-source
properties:
accessToken: "The Access Token"
accessTokenSecret: "The Access Token Secret"
apiKey: "The API Key"
apiKeySecret: "The API Key Secret"
user: "ApacheCamel"
sink:
ref:
kind: Channel
apiVersion: messaging.knative.dev/v1
name: mychannel
Make sure you have Camel K installed into the Kubernetes cluster you’re connected to.
Save the twitter-directmessage-source-binding.yaml
file into your hard drive, then configure it according to your needs.
You can run the source using the following command:
kubectl apply -f twitter-directmessage-source-binding.yaml
Dependencies
The Kamelet needs the following dependencies:
-
camel:jackson
-
camel:twitter
-
camel:kamelet
Binding to Knative using the Kamel CLI:
The procedure described above can be simplified into a single execution of the kamel bind
command:
kamel bind twitter-directmessage-source -p "source.accessToken=The Access Token" -p "source.accessTokenSecret=The Access Token Secret" -p "source.apiKey=The API Key" -p "source.apiKeySecret=The API Key Secret" -p "source.user=ApacheCamel" channel:mychannel
This will create the KameletBinding under the hood and apply it to the current namespace in the cluster.
Kafka Source
The twitter-directmessage-source
Kamelet can be used as Kafka source by binding it to a Kafka topic.
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: twitter-directmessage-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: twitter-directmessage-source
properties:
accessToken: "The Access Token"
accessTokenSecret: "The Access Token Secret"
apiKey: "The API Key"
apiKeySecret: "The API Key Secret"
user: "ApacheCamel"
sink:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
Ensure that you’ve installed Strimzi and created a topic named my-topic
in the current namespace.
Make also sure you have Camel K installed into the Kubernetes cluster you’re connected to.
Save the twitter-directmessage-source-binding.yaml
file into your hard drive, then configure it according to your needs.
You can run the source using the following command:
kubectl apply -f twitter-directmessage-source-binding.yaml
Binding to Kafka using the Kamel CLI:
The procedure described above can be simplified into a single execution of the kamel bind
command:
kamel bind twitter-directmessage-source -p "source.accessToken=The Access Token" -p "source.accessTokenSecret=The Access Token Secret" -p "source.apiKey=The API Key" -p "source.apiKeySecret=The API Key Secret" -p "source.user=ApacheCamel" kafka.strimzi.io/v1beta1:KafkaTopic:my-topic
This will create the KameletBinding under the hood and apply it to the current namespace in the cluster.