docs: Document --env flag for serverless create command#627
Conversation
Document the new --env flag for runpodctl serverless create that allows overriding or adding environment variables when deploying from Hub repos. Also clarify that --type filtering is applied client-side for hub commands.
| Execution timeout in seconds. Jobs that exceed this duration are terminated. The CLI accepts seconds but converts to milliseconds internally. | ||
| </ResponseField> | ||
|
|
||
| <ResponseField name="--env" type="string"> |
There was a problem hiding this comment.
Added --env flag documentation based on PR #262 in runpod/runpodctl. The flag uses KEY=VALUE format, supports multiple values, and overrides Hub release defaults when using --hub-id.
Source: runpod/runpodctl#262
|
|
||
| <ResponseField name="--type" type="string"> | ||
| Filter by deployment type (`POD` or `SERVERLESS`). | ||
| Filter by deployment type (`POD` or `SERVERLESS`). This filter is applied client-side, so `--limit` may return fewer results than specified. |
There was a problem hiding this comment.
Added client-side filtering note for --type flag based on PR #262 in runpod/runpodctl. The code in cmd/hub/list.go:198 and cmd/hub/search.go:274 shows the filter is applied client-side after API results are fetched.
Source: runpod/runpodctl#262
|
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.) |
Open this suggestion in Promptless to view citations and reasoning process
Add documentation for the new --env flag in runpodctl serverless create that allows overriding or adding environment variables when deploying from Hub repos. Also clarifies that --type filtering for hub list/search commands is applied client-side.
Trigger Events
Tip: Sort by Shortest Review in the Dashboard to find quick wins ⚡