검색

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 20. Has Header Filter Action

download PDF

Filter based on the presence of one header

20.1. Configuration Options

The following table summarizes the configuration options available for the has-header-filter-action Kamelet:

PropertyNameDescriptionTypeDefaultExample

name *

Header Name

The header name to evaluate. The header name must be passed by the source Kamelet. For Knative only, the name of the header requires a CloudEvent (ce-) prefix.

string

 

"headerName"

Note

Fields marked with an asterisk (*) are mandatory.

20.2. Dependencies

At runtime, the has-header-filter-action Kamelet relies upon the presence of the following dependencies:

  • camel:core
  • camel:kamelet

20.3. Usage

This section describes how you can use the has-header-filter-action.

20.3.1. Knative Action

You can use the has-header-filter-action Kamelet as an intermediate step in a Knative binding. For this example, the Knative mychannel provides a message header named ce-foo. The CloudEvents (ce-) prefix for the header name is required. The example in the Insert Header action shows how to add a message header to data.

has-header-filter-action-binding.yaml

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: has-header-filter-action-binding
spec:
  source:
    ref:
      kind: Channel
      apiVersion: messaging.knative.dev/v1
      name: mychannel
  steps:
  - ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: has-header-filter-action
    properties:
      name: "ce-foo"
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: log-sink

20.3.1.1. Prerequisites

  • Make sure you have "Red Hat Integration - Camel K" installed on the OpenShift cluster that you’re connected to.
  • The source Kamelet in the Kamelet Binding must pass a header with the name that you specify in the has-header-filter-action Kamelet’s name property.

20.3.1.2. Procedure for using the cluster CLI

  1. Save the has-header-filter-action-binding.yaml file to your local drive, and then edit it as needed for your configuration.
  2. Run the action by using the following command:

    oc apply -f has-header-filter-action-binding.yaml

20.3.1.3. Procedure for using the Kamel CLI

Configure and run the action by using the following command:

kamel bind channel:mychannel --step has-header-filter-action -p "step-0.name=ce-foo" log-sink

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

20.3.2. Kafka Action

You can use the has-header-filter-action Kamelet as an intermediate step in a Kafka binding. For this example, the kafka-source Kamelet provides a message header named foo. The example in the Insert Header action shows how to add a message header to data.

has-header-filter-action-binding.yaml

    apiVersion: camel.apache.org/v1alpha1
    kind: KameletBinding
    metadata:
      name: has-header-filter-action-binding
    spec:
      source:
        ref:
          kind: Kamelet
          apiVersion: camel.apache.org/v1alpha1
          name: kafka-source
        properties:
          bootstrapServers: "my-cluster-kafka-bootstrap.myproject.svc:9092"
          password: "XXX"
          topic: "my-topic"
          user: "XXX"
          securityProtocol: "PLAINTEXT"
      steps:
      - ref:
          kind: Kamelet
          apiVersion: camel.apache.org/v1alpha1
          name: has-header-filter-action
        properties:
          name: "foo"
      sink:
       ref:
          kind: Kamelet
          apiVersion: camel.apache.org/v1alpha1
          name: log-sink

20.3.2.1. Prerequisites

  • Ensure that you’ve installed the AMQ Streams operator in your OpenShift cluster and created a topic named my-topic in the current namespace.
  • Make sure that you have "Red Hat Integration - Camel K" installed on the OpenShift cluster that you’re connected to.

20.3.2.2. Procedure for using the cluster CLI

  1. Save the has-header-filter-action-binding.yaml file to your local drive, and then edit it as needed for your configuration.
  2. Run the action by using the following command:

    oc apply -f has-header-filter-action-binding.yaml

20.3.2.3. Procedure for using the Kamel CLI

Configure and run the action by using the following command:

kamel bind kafka-source -p "source.bootstrapServers=my-cluster-kafka-bootstrap.myproject.svc:9092" -p "source.password=XXX" -p "source.topic=my-topic" -p "source.user=XXX" -p "source.securityProtocol=PLAINTEXT" --step has-header-filter-action -p "step-0.name=foo" log-sink

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

20.4. Kamelet source file

https://github.com/openshift-integration/kamelet-catalog/blob/kamelet-catalog-1.6/has-header-filter-action.kamelet.yaml

Red Hat logoGithubRedditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

© 2024 Red Hat, Inc.