docs(runpodctl): drop --stop-after and --terminate-after - #820
Draft
justinwlin wants to merge 2 commits into
Draft
docs(runpodctl): drop --stop-after and --terminate-after#820justinwlin wants to merge 2 commits into
justinwlin wants to merge 2 commits into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This was referenced Aug 26, 2026
justinwlin
changed the title
justinwlin
force-pushed
the
justinlin/con-1258-stop-after-docs
branch
from
August 26, 2026 19:29
788efa6 to
86b22ea
Compare
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.
Follows runpod/runpodctl#330, which removes both flags.
They never worked. The timer was accepted, stored on no code path, and acted on by nothing — pods ran past the deadline and kept billing (CON-1258, customer refund). Documenting them as working is what led people to rely on them.
Removing the entries rather than correcting them, to match the remove-first plan: runpodctl#331 restores the flags with client-side validation, and runpod/RunPod#5718 makes the backend actually enforce the deadline. The docs go back when those land.
Also worth noting the entries were wrong on their own terms: they advertised durations (
1h,24h,7d), which the GraphQLDateTimescalar rejects.