uselagoon / uselagoon/lagoon-cli
CLI can't refresh auth token, crashing running process
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 14
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Describe the bug
I'm using the cli inside of a container. It's a guarantee that I will at some point hit this error while it is running and doing it's thing: Error: couldn't refresh token: unable to authenticate or connect to host 20.238.147.183:22 │ │ there may be an issue determining which ssh-key to use, or there may be an issue establishing a connection to the host │ │ the error returned was: ssh: handshake failed: EOF
To Reproduce
Steps to reproduce the behavior:
- login to lagoon cli using
lagoon login - wait 10-15 minutse
- run
lagoon loginagain and it should now hit the error shown in the picture above.
Expected behavior
preferably the CLI would have some sort of token refresh system in place making the need for refersh actions taken on the users side unnecessary.
Screenshots
Desktop (please complete the following information):
both in terminal and in pod
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 by tracing the token refresh path exercised by lagoon login, then reproduce the failure after waiting 10–15 minutes in a container. Done means authentication refreshes successfully and repeating lagoon login no longer returns the SSH handshake error or crashes the running CLI process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100