uselagoon / uselagoon/lagoon-cli
Lagoon shell
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 14
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
Having to type lagoon --project really-long-project-name --environment also-really-long-environment-name gets old.
Describe the solution you'd like
A REPL shell for Lagoon that stores some context (and shows it in the prompt). Context might include:
- $LAGOON_PROJECT
- $LAGOON_ENVIRONMENT
- An object type
This would mean that if your prompt said really-long-project-name also-really-long-environment-name variables that you could just write "list", and it would list the variables, and then "add", and it would add a variable to that project/environment.
Describe alternatives you've considered
- Making my bash prompt pick up on some $LAGOON_PROJECT/$LAGOON_ENVIRONMENT variables.
- Having Lagoon pick up on some predefined $LAGOON_PROJECT/$LAGOON_ENVIRONMENT variables. This would also be good to have (whether the suggestion above gets implemented or not).
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
The issue body names no files, tests, or entry points, so begin by mapping the existing Lagoon CLI command structure. Clarify the REPL scope and context model, then define completion around a prompt showing project, environment, and object type, with commands such as listing and adding variables using that context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100