-
Notifications
You must be signed in to change notification settings - Fork 424
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
Allow injection of sessions #1111
Conversation
Thanks for the contribution! Before we can merge this, we need @MrwanBaghdad to sign the Salesforce.com Contributor License Agreement. |
@jacalata Can you please take a look? |
Very nice! We do have another call where it sets _session = requests.Session() in the _set_auth() method - does that need to be overridden or updated somehow as well? I've also rebased this for you onto our new dev branch. |
within the server lifecycle specific usecase is when calling `_clear_auth`
@jacalata That's a good point. I've updated the PR to allow injection of a callable |
* Allow injection of sessions (#1111) * show server info (#1118) * Fix bug in exposing ExcelRequestOptions and test (#1123) * Fix a few pylint errors (#1124) * fix behavior when url has no protocol (#1125) * Add permission control for Data Roles and Metrics (Issue #1063) (#1120) * add option to pass specific datasources (#1150) * allow user agent to be set by caller (#1166) * Fix issues with connections publishing workbooks (#1171) * Allow download to file-like objects (#1172) * Add updated_at to JobItem class (#1182) * fix revision references where xml returned does not match docs (#1176) * Do not create empty connections list (#1178) --------- Co-authored-by: Marwan Baghdad <[email protected]> Co-authored-by: jorwoods <[email protected]> Co-authored-by: Brian Cantoni <[email protected]> Co-authored-by: TrimPeachu <[email protected]> Co-authored-by: Stu Tomlinson <[email protected]> Co-authored-by: Jeremy Harris <[email protected]>
This PR allows injection of
requests.Session
objects.This covers use cases when an end user may want to have more control over the session in case of proxies, custom authentication flows enforced by proxies in front of the Tableau server, and custom headers need to be injected to allow access to the Tableau server.