Retrive New Secrets on secret rotation

[Rishang]

A background task to fetch new secrets on a certain shudle

from teller we can retrive secrets and run in applications fetching those secrets via variables, but when my secrets change teller itself dosen't load my new secrets, so can there be a way to do'so

Currently I am exiting applications via health checks, which exits

[lreuven]

Hi @Rishang , Thanks for the issue, Can you share a bit more about what you are trying to achieve and the environment & flow you are running?

[drpdishant]

Hi @lreuven I am also facing the same issue, I am aware that currently teller is built assuming the local development environments, where devs can load env from various secret managers, and even local files. I that case once I have started teller with teller run, it will load the env into runtime, but it doesn't watch for the changes at the source. i.e If I update my local .env or, my AwS secret, or A vault secret, it won't update it on the go. To have it fetch the new values we have to exit the teller process and restart it to load with new values. This is a problem when I am using it to load secrets in Kubernetes pods, most of the times applications are built not to exit for missing environment config but rather throw the exception in logs. So without the pod getting restart it there's no way I can load the new values.

[kaplanelad]

Hey @drpdishant, Thank you for reaching out. Unfortunately, refreshing secrets is not currently on our roadmap. However, we would be more than happy to review any pull requests you may have.

In the meantime, I'll be closing this issue