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
Adapt to deprecations in superfly/flyctl#2733 #962
Conversation
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.
That's a lot of fly open
s! Left one comment.
apps/scale-count.html.markerb
Outdated
@@ -324,4 +324,4 @@ If a Machine is misbehaving (for instance, it's not `stop`ping successfully), yo | |||
fly machine destroy --force 0e286039f42e86 | |||
``` | |||
|
|||
<div class="callout"> If you `destroy` a Machine, any volume that it had been using still exists until you either `fly volumes delete` it or `fly destroy` the Fly App it belongs to.</div> | |||
<div class="callout"> If you `destroy` a Machine, any volume that it had been using still exists until you either `fly volumes delete` it or `fly apps destroy` the Fly App it belongs to.</div> |
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.
My preference would be not to use commands as verbs like this. In this case, remove the backticks from destroy in "If you destroy a Machine" and rewrite the rest something like "until you either delete the volume with the fly volumes delete
command or delete the app the volume belongs to with the fly apps destroy
command."
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.
Oh no! (not really oh no! I just prefer to use the command and backticks as I find it clearest)
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.
I tidied the callout. My reasoning here is that it's unnecessarily long to include all the commands.
* adapt to deprecations in superfly/flyctl#2733 * don't put nested commands in flyctl nav * Tidy callout language
This is a quick adaptation to recent flyctl changes (superfly/flyctl#2733). Replaces deprecated top-level commands with their
fly apps
equivalents in docs, and removes deprecated commands from the flyctl nav.