-
Notifications
You must be signed in to change notification settings - Fork 580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
endpoint.update() removes environment variables of endpoint #2472
Comments
Thanks for reporting the issue @MoritzLaurer! The problem comes from some |
Thanks for the quick fix @Wauplin ! What do you think about adding the |
Hi @MoritzLaurer this is indeed a separate feature request but luckily it has already been implemented: #2306 😃 You should be able to use it in |
What I meant is the |
Correct yes! Sorry about that 🙈 Fixed it in #2477 |
Describe the bug
I have an endpoint (e.g. TGI llama3.1 endpoint) with custom environment variables and secrets. When I update the endpoint, e.g. to get a new revision of the model, the model updates correctly, but the environment variables are lost.
The expected behaviour would be: Only the thing I'm specifying in
endpoint.update
(in this case, the model version fromrevision
) should change, while all the rest of the endpoint is not updated (i.e. the env variables remain the same). Interestingly enough: secrets are not deleted, while env variables are deleted.Reproduction
Create endpoint via endpoint interface and manually add env variable and secret.
The update endpoint does not contain the environment variable anymore.
The issue can be circumvented with
huggingface_hub.HfApi
by passing the env variables again viacustom_image
.In this case the env variables are preserved.
I think user's expected behaviour is that endpoint.update() preserves environment variables automatically (a customer reported this). If this is not possible, it would be good to add support for the
custom_image
argument inendpoint.update()
and document explicitly what gets lost if not passed to the method.Could you have a look at this @Wauplin ?
Logs
No response
System info
The text was updated successfully, but these errors were encountered: