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
{{ message }}
This repository was archived by the owner on Sep 22, 2025. It is now read-only.
For authentication, we currently have API_CREDENTIALS object which can be updated with authentication.authenticate_to_api. However, it would be nice to be able to specify a max timeout for an application globally instead of for each API call. This could be achieved potentially by adding a new object, _STRATODEM_API_CONFIG, which has entries for timeout (and potentially headers, or other configuration), then adding methods such as configuration.set_default_timeout that modify this object, which would be used as default if a user did not pass in a method-specific timeout.
User Story
As an API user with many queries, I want to be able to set a timeout for all of my queries at once instead of adding a keyword argument to each individually.
Description
For authentication, we currently have
API_CREDENTIALSobject which can be updated withauthentication.authenticate_to_api. However, it would be nice to be able to specify a max timeout for an application globally instead of for each API call. This could be achieved potentially by adding a new object,_STRATODEM_API_CONFIG, which has entries for timeout (and potentially headers, or other configuration), then adding methods such asconfiguration.set_default_timeoutthat modify this object, which would be used as default if a user did not pass in a method-specific timeout.User Story
As an API user with many queries, I want to be able to set a timeout for all of my queries at once instead of adding a keyword argument to each individually.