docs: Remove --stop-after and --terminate-after from runpodctl pod create reference - #829
Merged
lavanya-gunreddi merged 2 commits intoSep 1, 2026
Conversation
…eference These flags were removed from the CLI in runpod/runpodctl#330 because they were forwarded to the API but never enforced. Passing either now errors.
lavanya-gunreddi
approved these changes
Sep 1, 2026
Contributor
Author
|
Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.) |
promptless
Bot
deleted the
promptless/runpodctl-remove-stop-terminate-after
branch
September 1, 2026 21:58
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Open in Promptless
The
runpodctl pod createCLI reference listed--stop-afterand--terminate-afterflags that no longer exist. Both were removed from runpodctl because they were forwarded to the API but never enforced — Pods kept running (and billing) past the deadline, and passing either flag now returns anunknown flagusage error. This removes the two flag entries from the "Create flags" section ofrunpodctl/reference/runpodctl-pod.mdxso the reference matches the shipped CLI. No replacement flag exists, so no substitute is documented.Trigger Events
Tip: Enable auto-create PR in your Configuration to review suggestions directly in GitHub 🤖