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
It's a bit inconvenient for controlled deployment to a flock of machines, to have two files - .netrc + .config.yml - to deploy along with each other to have jira-cli work.
Idea would be
add an option to have API Token in config file, along with login and server
maybe as a precaution, check perms to be restrictive, in that case (user readonly)
during "jira init" after having asked for server + login, if no token is present in environment or from .netrc, prompt the user to paste one + put it into the config file
and maybe provide a "jira config edit (server|login|password)" option to change any of these, at a later time
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It's a bit inconvenient for controlled deployment to a flock of machines, to have two files - .netrc + .config.yml - to deploy along with each other to have jira-cli work.
Idea would be
Beta Was this translation helpful? Give feedback.
All reactions