All commands should use credentials
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
As per the documentation and my testing, not all gem commands support --key, which I interpret as them not using credentials from ~/.gem/credentials either.
Three of the possibly many commands that don't support --key or stored credentials are info, fetch and install. For commands like these, one has to jam authentication into the URL as such:
https://<username>:<password>@example.com
I think it would be good if all commands worked the same way regarding authentication and supported --key and ~/.gem/credentials consistently.
This issue is related to:
- Network problems
- Installing a library
- Publishing a library
- The command line
gem - Other
Here are my current environment details:
$ gem env version
3.0.6
I will abide by the code of conduct.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the command reference and the implementations of the named info, fetch, and install commands. Compare how --key and ~/.gem/credentials are handled against commands that already support them. Done means the commands use the same credential behavior consistently without requiring credentials embedded in URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100