OSD-24269: Add cluster login support via OHSS card

[samanthajayasinghe]

What type of PR is this?

feature

What this PR does / Why we need it?

Login cluster via JIRA ID

Which Jira/Github issue(s) does this PR fix?

Resolves #

Special notes for your reviewer

Unit Test Coverage

Guidelines

• If it's a new sub-command or new function to an existing sub-command, please cover at least 50% of the code
• If it's a bug fix for an existing sub-command, please cover 70% of the code

Test coverage checks

• Added unit tests
• Created jira card to add unit test
• This PR may not need unit tests

Pre-checks (if applicable)

• Ran unit tests locally
• Validated the changes in a cluster
• Included documentation changes with PR

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 67.74194% with 20 lines in your changes missing coverage. Please review.

Project coverage is 45.71%. Comparing base (5cbc36d) to head (252cbea).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #478      +/-   ##
==========================================
+ Coverage   45.50%   45.71%   +0.20%     
==========================================
  Files          71       72       +1     
  Lines        5900     5954      +54     
==========================================
+ Hits         2685     2722      +37     
- Misses       2878     2888      +10     
- Partials      337      344       +7     

Files	Coverage Δ
pkg/accessrequest/accessRequest.go	66.44% <100.00%> (ø)
pkg/jira/issueService.go	0.00% <ø> (ø)
pkg/jira/mocks/jiraMock.go	100.00% <ø> (ø)
pkg/jira/ohssService.go	70.96% <70.96%> (ø)
cmd/ocm-backplane/login/login.go	68.24% <57.69%> (-0.21%)	⬇️

[openshift-ci-robot]

@samanthajayasinghe: This pull request references OSD-24269 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.17.0" version, but no target version was set.

In response to this:

What type of PR is this?

feature

What this PR does / Why we need it?

Login cluster via JIRA ID

Which Jira/Github issue(s) does this PR fix?

Resolves #

Special notes for your reviewer

Unit Test Coverage

Guidelines

• If it's a new sub-command or new function to an existing sub-command, please cover at least 50% of the code
• If it's a bug fix for an existing sub-command, please cover 70% of the code

Test coverage checks

• Added unit tests
• Created jira card to add unit test
• This PR may not need unit tests

Pre-checks (if applicable)

• Ran unit tests locally
• Validated the changes in a cluster
• Included documentation changes with PR

Instructions 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 openshift-eng/jira-lifecycle-plugin repository.

[feichashao]

what is this file for?

[samanthajayasinghe]

unit test leftovers :)

[feichashao]

I hit an error,

 ./ocm-backplane login --ohss OHSS-xxxxx 
ERRO[0008] issue OHSS-xxxx is not belongs to OHSS project 

let me send you the OHSS ticket number offline.

[samanthajayasinghe]

I hit an error,

 ./ocm-backplane login --ohss OHSS-xxxxx 
ERRO[0008] issue OHSS-xxxx is not belongs to OHSS project 

let me send you the OHSS ticket number offline.

ahh ..nasty last-minute refactor mistake :(
Should be fixed now

[feichashao]

/label tide/merge-method-squash
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: feichashao, samanthajayasinghe

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [feichashao,samanthajayasinghe]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@samanthajayasinghe: all tests passed!

Full PR test history. Your PR dashboard.

Instructions 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.