You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If /etc/go-jira.yml is used to set the endpoint, then there is no reason for the user to create their ~/.jira.d directory manually.
This then leads to CmdLogin breaking, as it cannot save the cookies file:
2016-01-29T11:02:54.109Z ERROR [util.go:252] Failed to open /Users/mikepea/.jira.d/cookies.js: open /Users/mikepea/.jira.d/cookies.js: no such file or directory
The text was updated successfully, but these errors were encountered:
TL;DR, this ensures ~/jira.d is present, with 0755 perms.
If ~/jira.d isn't present, we can't write to the cookieFile, which
breaks CmdLogin. This is particularly an issue when using /etc/go-jira.yml
to get an entire team using go-jira easily :)
This fixes this by ensuring the cookieFile dir is present before
writing to it.
pdericson
pushed a commit
to pdericson/go-jira
that referenced
this issue
Sep 14, 2017
If
/etc/go-jira.yml
is used to set the endpoint, then there is no reason for the user to create their ~/.jira.d directory manually.This then leads to CmdLogin breaking, as it cannot save the cookies file:
The text was updated successfully, but these errors were encountered: