Saving cookies fails if ~/.jira.d is not present #32
Comments
coryb
added a commit
that referenced
this issue
Jan 29, 2016
Fixes #32 - make path to cookieFile if it's not present
pdericson
pushed a commit
to pdericson/go-jira
that referenced
this issue
Sep 14, 2017
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
Fixes go-jira#32 - make path to cookieFile if it's not present
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If
/etc/go-jira.ymlis 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: