Artifactory CLI should default to logging into an existing server
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 307
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 17
Description
Is your feature request related to a problem? Please describe.
I am annoyed that the UX of logging in to refresh my token, which I need to do all the time, defaults to configuring a new server, which I never do.
Describe the solution you'd like to see
I'd like to just have the jf login command log me in without suggesting I configure a new server.
Describe alternatives you've considered
- passing a bunch of flags to
jf c edit artifactory - pressing down arrow and enter every time I run
jf login(every day)
Additional context
❯ jfrog login
Use the arrow keys to navigate: ↓ ↑ → ←
Select whether to create a new server configuration or to web login to an existing one:
🐸 [New Server]
artifactory
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 at the jf login command flow and inspect how it selects between creating a new server configuration and logging into an existing one. Make an existing configured server the default while retaining the new-server option, then run jf login to verify the selection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100