oxidecomputer / oxidecomputer/console
Instance create form: clarify immediate creates vs. create on submit
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
We could add/are maybe planning to add a button that lets you create a floating IP right there, and that would cover it. The biggest issue for me is making clear which operations actually create stuff (e.g., floating IP, SSH key) and which are queuing things up to be created as part of instance create (e.g., disks). I wonder if the visual treatment could convey that somehow, or we can just put it in an info box at the top of the forms.
Originally posted by @david-crespo in https://github.com/oxidecomputer/console/issues/2252#issuecomment-2125205930
It's not clear what the behavior is when you add resources like disks and SSH keys on instance create, and we want the user to be able to click around and try things and know whether they're making real changes to the system.
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 instance create form and trace how floating IPs, SSH keys, and disks are handled when users add them. Done means the interface clearly distinguishes resources created immediately from those queued for instance creation, allowing users to understand the effect before submitting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100