Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support personal token authentication to jira (3.21.x) #1532

Merged
merged 1 commit into from
Jul 10, 2023
Merged

Support personal token authentication to jira (3.21.x) #1532

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 12 additions & 5 deletions kamelets/jira-add-comment-sink.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,10 +39,10 @@ spec:

The comment is set in the body of the message.

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -58,12 +58,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira
description: The password to access Jira
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
types:
in:
mediaType: application/json
Expand All @@ -88,5 +94,6 @@ spec:
uri: "jira:AddComment"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
access-token: "{{?personal-token}}"
17 changes: 12 additions & 5 deletions kamelets/jira-add-issue-sink.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,10 @@ spec:

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -70,12 +70,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira
description: The password to access Jira
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
types:
in:
mediaType: application/json
Expand Down Expand Up @@ -142,5 +148,6 @@ spec:
uri: "jira:AddIssue"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
access-token: "{{?personal-token}}"
18 changes: 13 additions & 5 deletions kamelets/jira-source.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,10 +32,11 @@ spec:
title: "Jira Source"
description: |-
Receive notifications about new issues from Jira.

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -51,12 +52,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira.
description: The password to access Jira.
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
jql:
title: JQL
description: A query to filter issues.
Expand All @@ -76,8 +83,9 @@ spec:
uri: "jira:newIssues"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
accessToken: "{{?personal-token}}"
jql: "{{jql}}"
steps:
- marshal:
Expand Down
17 changes: 12 additions & 5 deletions kamelets/jira-transition-issue-sink.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,10 +41,10 @@ spec:

The comment of the transition is set in the body of the message.

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -60,12 +60,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira
description: The password to access Jira
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
types:
in:
mediaType: application/json
Expand Down Expand Up @@ -97,5 +103,6 @@ spec:
uri: "jira:transitionIssue"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
access-token: "{{?personal-token}}"
17 changes: 12 additions & 5 deletions kamelets/jira-update-issue-sink.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,10 @@ spec:

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -70,12 +70,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira
description: The password to access Jira
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
types:
in:
mediaType: application/json
Expand Down Expand Up @@ -142,5 +148,6 @@ spec:
uri: "jira:UpdateIssue"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
access-token: "{{?personal-token}}"
17 changes: 12 additions & 5 deletions library/camel-kamelets/src/main/resources/kamelets/jira-add-comment-sink.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,10 +39,10 @@ spec:

The comment is set in the body of the message.

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -58,12 +58,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira
description: The password to access Jira
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
types:
in:
mediaType: application/json
Expand All @@ -88,5 +94,6 @@ spec:
uri: "jira:AddComment"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
access-token: "{{?personal-token}}"
17 changes: 12 additions & 5 deletions library/camel-kamelets/src/main/resources/kamelets/jira-add-issue-sink.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,10 @@ spec:

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -70,12 +70,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira
description: The password to access Jira
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
types:
in:
mediaType: application/json
Expand Down Expand Up @@ -142,5 +148,6 @@ spec:
uri: "jira:AddIssue"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
access-token: "{{?personal-token}}"
18 changes: 13 additions & 5 deletions library/camel-kamelets/src/main/resources/kamelets/jira-source.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,10 +32,11 @@ spec:
title: "Jira Source"
description: |-
Receive notifications about new issues from Jira.

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -51,12 +52,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira.
description: The password to access Jira.
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
jql:
title: JQL
description: A query to filter issues.
Expand All @@ -76,8 +83,9 @@ spec:
uri: "jira:newIssues"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
accessToken: "{{?personal-token}}"
jql: "{{jql}}"
steps:
- marshal:
Expand Down
17 changes: 12 additions & 5 deletions library/camel-kamelets/src/main/resources/kamelets/jira-transition-issue-sink.kamelet.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,10 +41,10 @@ spec:

The comment of the transition is set in the body of the message.

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.

required:
- jiraUrl
- username
- password
type: object
properties:
jiraUrl:
Expand All @@ -60,12 +60,18 @@ spec:
- urn:camel:group:credentials
password:
title: Password
description: The password or the API Token to access Jira
description: The password to access Jira
type: string
format: password
x-descriptors:
- urn:alm:descriptor:com.tectonic.ui:password
- urn:camel:group:credentials
personal-token:
title: Personal Token
description: Personal Token
type: string
x-descriptors:
- urn:camel:group:credentials
types:
in:
mediaType: application/json
Expand Down Expand Up @@ -97,5 +103,6 @@ spec:
uri: "jira:transitionIssue"
parameters:
jiraUrl: "{{jiraUrl}}"
username: "{{username}}"
password: "{{password}}"
username: "{{?username}}"
password: "{{?password}}"
access-token: "{{?personal-token}}"
Loading
Loading