google storage sink Google Storage Sink

Provided by: "Apache Software Foundation"

Support Level for this Kamelet is: "Stable"

Upload objects to Google Cloud Storage.

If you specify the serviceAccountKey property, you must base64 encode it before you pass it as a parameter.

In the header, you can set the file / ce-file property to specify the filename to upload. If you do set property in the header, the Kamelet uses the exchange ID as filename.

Configuration Options

The following table summarizes the configuration options available for the google-storage-sink Kamelet:

Property Name Description Type Default Example

bucketNameOrArn

Bucket Name Or ARN

Required The Google Cloud Storage bucket name or Bucket Amazon Resource Name (ARN).

string

autoCreateBucket

Autocreate Bucket

Specifies to automatically create the Google Cloud Storage bucket.

boolean

false

serviceAccountKey

Service Account Key

The service account key to use as credentials for Google Cloud Storage access. You must encode this value in base64.

binary

Dependencies

At runtime, the google-storage-sink Kamelet relies upon the presence of the following dependencies:

  • camel:core

  • camel:kamelet

  • camel:google-storage

  • camel:jackson

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:log-sink"

You can now run it directly through the following command

camel run route.yaml

Camel K Environment Usage

This section describes how you can use the google-storage-sink.

Knative sink

You can use the google-storage-sink Kamelet as a Knative sink by binding it to a Knative object.

google-storage-sink-pipe.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: google-storage-sink-pipe
spec:
  source:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: google-storage-sink
    properties:
      bucketNameOrArn: The Bucket Name Or ARN

Prerequisite

You have Camel K installed on the cluster.

Procedure for using the cluster CLI

  1. Save the google-storage-sink-pipe.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command:

    kubectl apply -f google-storage-sink-pipe.yaml

Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind google-storage-sink -p "sink.bucketNameOrArn=The Bucket Name Or ARN" channel:mychannel

This command creates the Kamelet Pipe in the current namespace on the cluster.

Kafka sink

You can use the google-storage-sink Kamelet as a Kafka sink by binding it to a Kafka topic.

google-storage-sink-pipe.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: google-storage-sink-pipe
spec:
  source:
    ref:
      kind: KafkaTopic
      apiVersion: kafka.strimzi.io/v1beta1
      name: my-topic
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: google-storage-sink
    properties:
      bucketNameOrArn: The Bucket Name Or ARN

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 google-storage-sink-pipe.yaml file to your local drive, and then edit it as needed for your configuration.

  2. Run the sink by using the following command:

    kubectl apply -f google-storage-sink-pipe.yaml

Procedure for using the Kamel CLI

Configure and run the sink by using the following command:

kamel bind google-storage-sink -p "sink.bucketNameOrArn=The Bucket Name Or ARN" kafka.strimzi.io/v1beta1:KafkaTopic:my-topic

This command creates the Kamelet Pipe in the current namespace on the cluster.