Setting up CD for serverless endpoint
I tried the GitHub integration but our Docker image base is a private image so the build system needs to support using credentials
I also tried the Docker image approach - this works great for our pre-built images but how can I setup CD for this?
9 Replies
CD like what process?
You can send a request to runpod's graphql to change template's container image slot

then the serverless endpoint will sync up to the new template ( new image tag ), side note: dont use the same tag too
Which graphql mutation should I look at?
I looked here before but didn't find any function exposed to update endpoints or templates.

CD as in Continuous Delivery. When new version of the image is pushed to the registry, how can I programmatically tell runpod update our template or endpoint?
Manage to find the endpoint through browser network inspection. Not the best since this is an undocumented (likely internal api).
It is not documented I think but yes you can use it too since it's a graphql api
Yes it is not well documented, you can go ahead to web UI and view Network tab requests
The request got triggered when clicking New Release -> Save the request you need, you can copy it via CURL, remove headers and put api key, then you will be changin imageName there when you want to release a new image
This updates Template image that endpoint uses
it's the one with
mutation saveTemplate($input: SaveTemplateInput) {
ill get team to add this to docs