spinframework / spinframework/spin
How to sustain usability with an increasing number of `spin up` flags
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
From a comment from @radu-matei on #1477:
... even with this in place, I am a bit concerned that as we continue to add features, this is starting to become unsustainable — both for spin up and for spin deploy.
On one hand, I really like the simplicity of just running a CLI command. But on the other, after a certain number of flags, you are approaching the need for a configuration file?
Not sure what the ideal solution would look like here.
Breaking this out into a separate issue from the grouping one (acknowledging that if we did, say, entirely replace the options with a config file then the grouping problem would go away).
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 spin up and spin deploy CLI flags are currently organized, then read the related discussion in #1477. The issue does not name files or tests, so first identify the relevant command and option definitions. Done requires an agreed approach for sustaining usability as the number of flags grows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100