Enable Jira Cloud Basic auth for firewatch report step#76544
Enable Jira Cloud Basic auth for firewatch report step#76544openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Conversation
Update the firewatch-report-issues step to support Jira Cloud Basic auth (email + API token) required after the migration to Atlassian Cloud. Bearer token auth returns HTTP 403 on write operations (issue updates, label changes) with "Failed to parse Connect Session Auth Token". Changes: - Update default JIRA_SERVER to https://redhat.atlassian.net - Add FIREWATCH_JIRA_EMAIL_PATH env var (reads from credential secret) - Pass --email to jira-config-gen when the email file exists Requires adding an 'email' key to the firewatch-tool-jira-credentials secret in the test-credentials namespace. Made-with: Cursor
openshift-ci
bot
added
the
approved
|
[REHEARSALNOTIFIER]
A total of 484 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/lgtm |
|
/lgtm |
|
/pj-rehearse ack |
|
@amp-rh: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amp-rh, oharan2, sg-rh, shakyav The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@amp-rh: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
5 participants
Summary
Update the
firewatch-report-issuesstep to support Jira Cloud Basic auth (email + API token) after the migration to Atlassian Cloud (redhat.atlassian.net).Problem
After Jira migrated to Atlassian Cloud, firewatch write operations fail:
Content-Type 'null' is not supportedFailed to parse Connect Session Auth TokenBearer token auth works for read operations (search, connection) but fails on writes (issue updates, label changes). Jira Cloud requires Basic auth (email + API token) for write operations.
Changes
firewatch-report-issues-ref.yaml:FIREWATCH_JIRA_SERVERfromhttps://issues.redhat.comtohttps://redhat.atlassian.netFIREWATCH_JIRA_EMAIL_PATHenv var (defaults to/tmp/secrets/jira/email)firewatch-report-issues-commands.sh:--emailtojira-config-genwhen the email file exists in the credential secretPrerequisites
An
emailkey must be added to thefirewatch-tool-jira-credentialssecret in thetest-credentialsnamespace containing the service account email for Jira Cloud.Related
/cc @sg-rh @oharan2
Made with Cursor