Config entry for each Jira instance and its credentails

[electriquo]

Thank you for the JiraCLI.

JiraCLI requires to expose Jira API Token (or password) and maybe tweaking the authentication type for Jira CLI to work. One might even consider other means of exposing Jira API Token (or password).

The process above needs to be repeated for every Jira instance.
After the process was done, the modified files (e.g. .bashrc, .netrc, etc.) should not be stored under Source Control Management (SCM) such as GIt due to the sensitivity of the credentials in these files.

What about letting jira init to open the internet browser and point it to Jira API Tokens, then wait for the user to type in the API token once created. In turn JiraCLI will create a file $HOME/.config/.jira/.config.yml with all the configuration and the credentials in the same spirit GitHub CLI keeps such configuration and credentials?

This will:

1. Allow to exclude the file from SCM tracking and without compromising any credentials leakage into the profile file, which cannot be excluded from the SCM for obvious reasons
2. Streamline the authentication processes by removing the requirement to (a) read all the instructions on how to set the token, (b) modifying any files manually, especially will discard the modification of broad user files, and (c) easing the management of such many configurations using --config.

related to #356, #434, #268, #217, #287 (and maybe some others).

[ankitpokhrel]

Hi @foolioo, thank you for opening this thread. I think this is a valid concern and something that could be improved (I am open for PRs).

Having said that, there are a ton of things that GitHub CLI does better and can be borrowed to make JiraCLI better. But, right now its just a single person maintaining this project and I am trying my best to make the tool usable for majority of use cases. Any kind of support is highly appreciated.

[electriquo]

Thank you for all your efforts!

I would really love to contribute, but I won't be of any help as I am not fluent in Go.
I've included a link to GitHub CLI implementation, maybe it will give a lead to one who can contribute to the project.

Right now, this thing kinda blocks me from adopting Jira CLI and enjoy your work.
Do you think we should convert this discussion into a feature request?

[electriquo]

@ankitpokhrel Do you think we should convert this discussion into a feature request?