-
Notifications
You must be signed in to change notification settings - Fork 19
Update copy regarding disk attach / detach requirements #2207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| Instance must be <span className="text-default">stopped</span> to create a | ||
| disk | ||
| </> | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could it be worth saying “create and attach” here? it’s the attach that’s the problem, right?
| <>Instance must be in state {detachableStates} before disk can be detached</> | ||
| <> | ||
| Instance must be <span className="text-default">stopped</span> before disk can | ||
| be detached |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might as well do what the other ones do, fudge it grammatically to save a few words: “instance must be stopped to detach disks” or maybe even “instance must be stopped” by itself? the button is disabled and it says “detach”
david-crespo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, not particularly attached to my comments!
oxidecomputer/console@e7b243b...31d1884 * [31d18845](oxidecomputer/console@31d18845) oxidecomputer/console#2194 * [86c44035](oxidecomputer/console@86c44035) oxidecomputer/console#2199 * [d9adfce3](oxidecomputer/console@d9adfce3) fix npm run start:mock-api by switching to tsx * [042d5ef3](oxidecomputer/console@042d5ef3) oxidecomputer/console#2209 * [e45f2d9a](oxidecomputer/console@e45f2d9a) oxidecomputer/console#2207 * [e8e4f576](oxidecomputer/console@e8e4f576) react 18.3.1 (fix test warnings due to act export)
oxidecomputer/console@e7b243b...31d1884 * [31d18845](oxidecomputer/console@31d18845) oxidecomputer/console#2194 * [86c44035](oxidecomputer/console@86c44035) oxidecomputer/console#2199 * [d9adfce3](oxidecomputer/console@d9adfce3) fix npm run start:mock-api by switching to tsx * [042d5ef3](oxidecomputer/console@042d5ef3) oxidecomputer/console#2209 * [e45f2d9a](oxidecomputer/console@e45f2d9a) oxidecomputer/console#2207 * [e8e4f576](oxidecomputer/console@e8e4f576) react 18.3.1 (fix test warnings due to act export)
Currently, we have some copy on the Storage tab of the Instance page, where we tell the user that certain conditions have to be met (the instance has to be stopped) before the user can take specific actions (detaching the disk). There's some other copy that — while technically accurate (probably) — aren't things that the user really cares about in that moment.
This PR updates that view, so that the thing the user needs to know — you need to stop the instance in order to detach the disk, or add a new disk — is more clearly linked to the next step they need to take — stopping the instance.

I'm open to copy suggestions, as always, though I think what I have here is pretty clear.