Repository navigation
fix(runpod): migrate one-shot jobs from retired REST v1 to v2 - #283
Merged
Merged
Conversation
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
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.
Fixes #282.
RunPod's current overview says REST v1 is no longer available. Migrate the one-shot launcher to https://api.runpod.io/v2, including nested create fields, explicit entrypoint/CMD, CUDA constraints under gpu, and the top-level cost response field. Explicitly preserve v1's default 20 GB /workspace persistent mount. The removed download-speed filter is now a deprecated compatibility flag with a warning.
Cleanup uses DELETE /v2/pods/{id}, no request body, empty HTTP 204 response. Exhausted termination attempts now raise an error so the launcher cannot silently succeed or create another host while the previous pod may still be billing. Retain GraphQL uptime polling. Update manual sweep guidance and keep all three skill copies identical. Add 13 offline contract/lifecycle tests.
Official documentation checked November 17, 2026:
SDK audit: requirements-cloud.txt specifies runpod>=1.7.0, not an exact pin. Minimum-version source and installed 1.12.0 use GraphQL for pod create/get/terminate, so no SDK requirement or backend change is needed for the REST v1 shutdown.
Validation:
Live test left for Joseph (not performed here):
🤖 Generated with Claude Code