Runpod•5mo ago

Configuring endpoints via API if publishing via Github integration

It seems that there's no way to create / update endpoints via the API, unless you host the images on a docker registry.
Are there plans to extend API support to endpoints that are published from a github branch?

Jason•7/30/25, 2:14 AM

What do you mean?

Jason•7/30/25, 2:14 AM

update endpoints via api, what do you want to update?

red_wolfOP•7/30/25, 6:28 AM

I want to have my full endpoint configuration and deployment via code: Version controlled, sharable, readable in plain text, ...

But this doesn't seem to be possible using the github integration, as opposed to deploying from a container registry.

Rred_wolf I want to have my full endpoint configuration and deployment via code: Version ...

Jason•7/30/25, 6:39 AM

you mean clone endpoint?

Rred_wolf I want to have my full endpoint configuration and deployment via code: Version ...

Jason•7/30/25, 6:39 AM

why do you want to do that?

Jason•7/30/25, 6:40 AM

or perhaps you want to share it publicly? (the hub)

JJason why do you want to do that?

red_wolfOP•7/30/25, 7:56 AM

collaboration: others in the team can easily view, review, ... the configuration
documentation: I need to write separate docs that instruct how to click something and where to put which value in the ui, rather than having a copy pastable command or script that i can run...
ui is buggy, ui is slow, ui is not searchable like api docs would be, ui changes are not traceable like versioned api changes would be
LLMs have and will continue to have a hard time with UIs ... see also: https://x.com/karpathy/status/1914489538006933770
version control + having everything in one place (my git repository)
automation/scripting, ...
and also sharing publicly would be way, way easier, than having to go trough the tedious process of publishing something on the hub ... (which is restrictive in more than one way, e.g. that I can't (or at least I didnt find a straightforward way to) share mutiple versions of a template from the same repo (using the same handler or other common parts in a codebase, or a different docker file); a change in the iconUrl triggers a full rebuild, ..., ...

Andrej Karpathy (@karpathy)

The docs also have to change in the content. Eg instead of instructing a person to go to some page and do this or that, they could show curl commands to run - actions that are a lot easier for an LLM to carry out.

Products have to change to support these too. Eg adding a

•

4/22/25, 1:20 AM

Jason•7/30/25, 8:04 AM

not this?

JJason not this?

Jason•7/30/25, 8:04 AM

Whats missing / not working with github repo endpoints

JJason Whats missing / not working with github repo endpoints

red_wolfOP•7/30/25, 8:48 AM

From my findings, but I might be wrong:

GitHub templates are not regular templates:
   - They appear in template list but return 404 on direct access
   - They have auto-generated names like "[endpoint name]__template__00vc58"
   - Images are built and stored in RunPod's private registry: registry.runpod.net/{user}-{repo}-{branch}-{dockerfile}:{commit}
What you CAN update via API:
   - All endpoint settings (workers, timeouts, scaling, etc.)
   - Switch between different template versions
   - Endpoint name and configuration
What you cannot update via API:
   - Template environment variables
   - Docker CMD/ENTRYPOINT overrides
   - Container disk size
   - Any template-level settings

GitHub templates are not regular templates:
   - They appear in template list but return 404 on direct access
   - They have auto-generated names like "[endpoint name]__template__00vc58"
   - Images are built and stored in RunPod's private registry: registry.runpod.net/{user}-{repo}-{branch}-{dockerfile}:{commit}
What you CAN update via API:
   - All endpoint settings (workers, timeouts, scaling, etc.)
   - Switch between different template versions
   - Endpoint name and configuration
What you cannot update via API:
   - Template environment variables
   - Docker CMD/ENTRYPOINT overrides
   - Container disk size
   - Any template-level settings

Rred_wolf From my findings, but I might be wrong: ``` GitHub templates are not regular t...

Jason•7/30/25, 9:25 AM

can you put this under #

｜api-opensource or #

｜feedback please

Jason•7/30/25, 9:26 AM

thanks for the detailed explanation

GitHub templates are not regular templates: - They appear in template list but return 404 on direct access - They have auto-generated names like "[endpoint name]__template__00vc58" - Images are built and stored in RunPod's private registry: registry.runpod.net/{user}-{repo}-{branch}-{dockerfile}:{commit} What you CAN update via API: - All endpoint settings (workers, timeouts, scaling, etc.) - Switch between different template versions - Endpoint name and configuration What you cannot update via API: - Template environment variables - Docker CMD/ENTRYPOINT overrides - Container disk size - Any template-level settings

Configuring endpoints via API if publishing via Github integration

Similar Threads

Similar Threads

Similar Threads