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.

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

Migrate away from deprecated gajira* actions (OSOE-722) #275

Closed
Piedone opened this issue Nov 9, 2023 · 6 comments · Fixed by #327
Closed

Migrate away from deprecated gajira* actions (OSOE-722) #275

Piedone opened this issue Nov 9, 2023 · 6 comments · Fixed by #327
Assignees

Comments

@Piedone
Copy link
Member

Piedone commented Nov 9, 2023

We use Atlassian's own gajira* actions (like https://github.com/atlassian/gajira-login and https://github.com/atlassian/gajira-create) to interact with Jira. However, these are deprecated and there's no official guidance on what to use instead of them (see atlassian/gajira#18). They also use the now deprecated v16 of Node.js. So, we should figure out what to use instead.

Most possibly we can interact with the Jira RESTful API directly from PowerShell, or perhaps there's some PS module to make this easier too. We can also check out https://github.com/ankitpokhrel/jira-cli.

Jira issue

@github-actions github-actions bot changed the title Migrate away from deprecated gajira* actions Migrate away from deprecated gajira* actions (OSOE-722) Nov 9, 2023
@BenedekFarkas
Copy link
Member

BenedekFarkas commented Nov 9, 2023

We can try maintaining (fork) them and or even take over stewardship of these (both have a few dozen stars, so we could put our name in front of a new audience) unless it's significantly harder than just calling the API, but I guess a breaking change would affect both kinds of tools the same way.

@Piedone
Copy link
Member Author

Piedone commented Nov 9, 2023

Yeah, that would be an option as well.

@Piedone
Copy link
Member Author

Piedone commented Nov 9, 2023

For now, what needs to be done to keep these actions working in the mid-term, is updating their Node.js version from 16 to 20. They'll use v20 in any case from some time next spring (see https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/), at which point they might break.

@Piedone
Copy link
Member Author

Piedone commented Nov 12, 2023

We need better restrictions for such API access, so instead, we should do #277.

@Piedone
Copy link
Member Author

Piedone commented Feb 10, 2024

This is again needed, see #277 (comment)

@Piedone
Copy link
Member Author

Piedone commented Feb 12, 2024

Looked into using https://github.com/AtlassianPS/JiraPS. However, the latest release of it is from 4 years ago (even though there are recent updates in the repo), not much activity in the issue tracker, and we'd need to work around it not having a feature to add remote links: AtlassianPS/JiraPS#375.

Looked into https://github.com/ankitpokhrel/jira-cli too. That looks great, but seems more of an interactive CLI than something suited for unattended scripts. Installing it would be uneasy too.

So, we'll go with vanilla PS for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants