You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw that dynamic headers are already supported in unleash-client-node and unleash-client-java.
I was wondering if there's an implementation of this feature in unleash-client-python.
If none, what is your recommended work around?
Thank you!
The text was updated successfully, but these errors were encountered:
Modifying the unleash_custom_headers class variable (a plain old dictionary) on the client will update the request headers the next time the client sends an API request to the server.
Having said that, I've mainly done this using integration scripts for testing purposes. Could you let me know how it works for you? (If it works great, I'll add it to the documentation.)
Hi @ivanklee86,
I test your scenario, unleash_custom_headers are being updated but the workers still using the headers from the client initialization. I validated it by logging the headers on my unleash client and on my python test script using the unleash-client-python
I tried to re-initialize the client using client.initialize_client() after changing the headers in the assumption that it would also re-initialize the workers but it raises this error:
raise SchedulerAlreadyRunningError
apscheduler.schedulers.SchedulerAlreadyRunningError: Scheduler is already running
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I got the same problem with Support for setting headers dynamically from unleash-client-node but mine is for Python.
I saw that dynamic headers are already supported in unleash-client-node and unleash-client-java.
I was wondering if there's an implementation of this feature in unleash-client-python.
If none, what is your recommended work around?
Thank you!
The text was updated successfully, but these errors were encountered: