uselagoon / uselagoon/lagoon-cli
Add support for a private key to be defined via a environment variable.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 14
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Primarily for use in CI systems it would be good to be able to pass a private key via an environment variable to the CLI to be used as the default key for authentication.
eg. docker run --rm -e SSH_KEY=[private_key] amazeeio/lagoon-cli list projects
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 Lagoon CLI entry point and trace how the default authentication key is selected. Check the Docker invocation in the issue as the manual verification path, then confirm that setting SSH_KEY allows the CLI to authenticate without another key configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100