feat: add registry auth and port labels to templates - #290
Closed
kodxana wants to merge 1 commit into
Closed
Conversation
|
Promptless prepared a documentation update related to this change. Triggered by runpodctl PR #290 Documents the new Review: Document runpodctl template registry auth and port label flags |
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.
summary
--registry-auth-idtotemplate createandtemplate updatetemplate update --registry-auth-id ""to detach registry credentials--port-labelsto template create/update, with shorthand (22=ssh,8888=jupyter lab) and JSON formscontainerRegistryAuthIdandportsConfigin template outputimplementation
registry auth is sent through the existing REST template create/update paths.
port labels use the GraphQL
portsConfigfield through a narrow supplementalsaveTemplatemutation. before that mutation, the CLI loads and preserves the complete existing template state. values changed by the immediately preceding REST request are overlaid so a briefly stale GraphQL read cannot undo the update.create validates labels against
--portsand removes the newly created template if the label mutation fails. update supports clearing labels with--port-labels ""and reports when REST fields succeeded but the label mutation failed.examples
validation
RUNPOD_API_KEYis available in this environment