Skip to content
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

Merged
merged 3 commits into from Sep 4, 2023
Merged

Conversation

catflydotio
Copy link
Contributor

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.

Copy link
Contributor

@andie787 andie787 left a 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 opens! Left one comment.

@@ -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>
Copy link
Contributor

@andie787 andie787 Sep 4, 2023

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."

Copy link
Contributor Author

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)

Copy link
Contributor Author

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.

@catflydotio catflydotio merged commit a2ae162 into main Sep 4, 2023
1 check passed
@catflydotio catflydotio deleted the flyctl-deprecations branch September 4, 2023 19:19
bradgessler pushed a commit that referenced this pull request Sep 29, 2023
* adapt to deprecations in superfly/flyctl#2733

* don't put nested commands in flyctl nav

* Tidy callout language
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants