Red Hat SummitChapter 35. Jira Add Issue Sink
Add a new issue to Jira.
The Kamelet expects the following headers to be set:
-
projectKey/ce-projectKey: as the Jira project key. -
issueTypeName/ce-issueTypeName: as the name of the issue type (example: Bug, Enhancement). -
issueSummary/ce-issueSummary: as the title or summary of the issue. -
issueAssignee/ce-issueAssignee: as the user assigned to the issue (Optional). -
issuePriorityName/ce-issuePriorityName: as the priority name of the issue (example: Critical, Blocker, Trivial) (Optional). -
issueComponents/ce-issueComponents: as list of string with the valid component names (Optional). -
issueDescription/ce-issueDescription: as the issue description (Optional).
The issue description can be set from the body of the message or the issueDescription/ce-issueDescription in the header, however the body takes precedence.
To authenticate, a username/password or personal token must be defined. We recommend to use personal token as it is a safer way to get access to Jira.
35.1. Configuration Options
The following table summarizes the configuration options available for the jira-add-issue-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| jiraUrl * | Jira URL | The URL of your instance of Jira | string | ||
| password | Password | The password to access Jira | string | ||
| personal-token | Personal Token | Personal Token | string | ||
| username | Username | The username to access Jira | string |
* = Fields marked with an asterisk are mandatory.
35.2. Dependencies
35.2.1. Quarkus dependencies
<dependencies>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifact>camel-quarkus-core</artifact>
</dependency>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifact>camel-quarkus-jackson</artifact>
</dependency>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifact>camel-quarkus-jira</artifact>
</dependency>
<dependency>
<groupId>org.apache.camel.quarkus</groupId>
<artifact>camel-quarkus-kamelet</artifact>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.datatype</groupId>
<artifact>jackson-datatype-joda</artifact>
<version>2.12.5</version>
</dependency>
<dependency>
<groupId>org.apache.camel.kamelets</groupId>
<artifact>camel-kamelets-utils</artifact>
<version>4.8.5</version>
</dependency>
</dependencies>35.3. Usage
35.3.1. Camel JBang usage
35.3.1.1. Prerequisites for JBang
- Install JBang.
You have executed the following command:
jbang app install camel@apache/camel
35.3.1.2. Running a route with JBang
Suppose 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.yaml35.3.2. Knative Sink
You can use the jira-add-issue-sink Kamelet as a Knative sink by binding it to a Knative object.
jira-add-issue-sink-binding.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: jira-add-issue-sink-binding
spec:
source:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
steps:
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: insert-header-action
properties:
name: "projectKey"
value: "MYP"
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: insert-header-action
properties:
name: "issueTypeName"
value: "Bug"
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: insert-header-action
properties:
name: "issueSummary"
value: "The issue summary"
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: insert-header-action
properties:
name: "issuePriorityName"
value: "Low"
sink:
ref:
kind: Channel
apiVersion: messaging.knative.dev/v1
name: mychannel
properties:
jiraUrl: "jira server url"
username: "username"
password: "password"35.3.3. Kafka Sink
You can use the jira-add-issue-sink Kamelet as a Kafka sink by binding it to a Kafka topic.
jira-add-issue-sink-binding.yaml
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: jira-add-issue-sink-binding
spec:
source:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
steps:
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: insert-header-action
properties:
name: "projectKey"
value: "MYP"
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: insert-header-action
properties:
name: "issueTypeName"
value: "Bug"
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: insert-header-action
properties:
name: "issueSummary"
value: "The issue summary"
- ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: insert-header-action
properties:
name: "issuePriorityName"
value: "Low"
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: jira-add-issue-sink
properties:
jiraUrl: "jira server url"
username: "username"
password: "password"
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}