uselagoon / uselagoon/lagoon-cli
use LAGOON_CONFIG_x vars to create the default cluster to operate on
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 14
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Lagoon CLI should be able to use the variables in https://github.com/uselagoon/build-deploy-tool/pull/193 to configure a default cluster (without a ~/.lagoon.yml file present)
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 reviewing how the Lagoon CLI currently selects a default cluster and reads ~/.lagoon.yml, then inspect the configuration variables introduced in build-deploy-tool PR 193. The change is done when those LAGOON_CONFIG_x variables configure a default cluster when ~/.lagoon.yml is absent; no specific files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100