uselagoon / uselagoon/lagoon-cli
Cut-down developer-focused version of the CLI
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.
Some Lagoon operators would like to provide developers with a simplified version of the CLI so that there is less to learn / break. For example it would be nice to facilitate common developer workflows without advertising the ability to update (break) user/group permissions etc.
Describe the solution you'd like
I'm not sure what actions would be required. Probably:
- Edit environment variables
- Trigger Deployments (on non-prod, this will be enforced by RBAC)
- ??? (please request in the comments!)
Describe alternatives you've considered
The current CLI is great but has functionality which we might not want to advertise to avoid breaking certain bespoke Lagoon installs.
Additional context
n/a
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 names no files, commands, or tests. Start by inventorying the existing CLI actions, especially environment-variable editing, deployment triggers, and permission-related operations, then determine how a developer-focused subset would be defined and enforced. Done means the supported scope and its behavior are agreed and documented.
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
- Needs clarification
- Newbie friendliness
- 25/100