We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The gajira-login action creates $HOME/.jira.d/credentials however the CLI does not seem to read it.
$HOME/.jira.d/credentials
The text was updated successfully, but these errors were encountered:
@rocketraman redditblog
Sorry, something went wrong.
I'm experiencing the same issue with this workflow:
--- name: Jira CLI on: push jobs: jira_session: runs-on: ubuntu-latest steps: - name: Setup id: setup_jira_cli uses: atlassian/[email protected] - name: Login to Jira id: login_jira uses: atlassian/[email protected] env: JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }} JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }} JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }} - name: Open session id: open_session run: jira session
This results in the following failure due to prompting for the API-Token:
Run jira session jira session shell: /usr/bin/bash -e {0} ERROR EOF ? Jira API-Token [***]: [? for help] 25l Error: Process completed with exit code 1.
Similar flows using other Actions (i.e., Create issue) have no issues performing authenticated actions.
A workaround is to add the JIRA_API_TOKEN to the cli action:
JIRA_API_TOKEN
env: JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
No branches or pull requests
The gajira-login action creates
$HOME/.jira.d/credentials
however the CLI does not seem to read it.The text was updated successfully, but these errors were encountered: