KingHarry
RRunPod
•Created by KingHarry on 12/23/2024 in #⚡｜serverless
Environment Variables Crossing Serverless Endpoints
Yes, it did change the template itself.
Odd, I guess my use case is not the intended one for templates and the copy endpoint functionality. I expected templates and copied endpoints to support distinct overrides for the templated values once the endpoint is created. Especially the env vars.
Is the main use case for templates and endpoint copies to change the worker infra options and regions?
Thanks for escalating - hopefully we can at least get the UI updated to make it clear you are editing the template for those fields and editing the endpoint for fields that are distinct per copy.
10 replies
RRunPod
•Created by KingHarry on 12/23/2024 in #⚡｜serverless
Environment Variables Crossing Serverless Endpoints
I have an existing template:
worker-template
I create an endpoint with it and set some env vars
endpoint-1
I copy the endpoint and change the docker image it is using and set the same env var keys with different values
endpoint-2
I copy the endpoint again and change the docker image it is using and set the same env var keys with different values
endpoint-3
Then I go back and look at endpoint-1 and endpoint-2 and they have the same env var values as endpoint-3.
I never edit the template. I click "edit endpoint" for each of the updates to change the docker image and the env vars.
I just noticed that the docker image does the same thing as the env vars. So I guess "edit endpoint" is really "edit template" or something other than what I thought...
10 replies