-
Notifications
You must be signed in to change notification settings - Fork 393
adapters: if session
is user-supplied, do not overwrite session options with Client
/Adapter
options
#1021
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
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1021 +/- ##
==========================================
+ Coverage 85.02% 85.08% +0.06%
==========================================
Files 65 65
Lines 3139 3145 +6
==========================================
+ Hits 2669 2676 +7
+ Misses 470 469 -1
|
Hey @Tylerlhess thanks for this. I haven't looked at it fully yet, but I wanted to mention I opened #1023 to try to deal with our out-of-date Vault versions in the integration tests. My hope is we can get all the issues ironed out in there so that you don't have to add these unrelated changes into your PR. I've already borrowed your azure fix (with attribution) in b01e796 though since we're also not pinning to I really appreciate you bringing these issues to our attention! |
With #1023 & #1024 merged, those should fix the Azure failures, SSH failures you saw locally, and the coverage issues, so you can rebase against or merge from the latest
Issue resolved, was on my end. The other changes in the PR look good to me, the only other thing I'd like to do is add warnings for users who are affected, telling them that in a future major version we'll stop applying any overrides from the affected parameters when a session is supplied. I can also add that stuff in alongside the work you've done already. |
session
is user-supplied, do not overwrite session options with Client
/Adapter
options
Looks like those changes have resolved the issues that would be happening in 1.12 and 1.13. |
Fixes: #991
Breaking change
For more details see also:
Before this change:
session
, a session is created for you with values for theverify
,cert
, andproxies
settings that are set in the adapter, either explicitly or by defaultsession
:session
will always be overwritten with the adapter values, whether you specified them or notAfter this change:
session
, a session is created for you with values for theverify
,cert
, andproxies
settings that are set in the adapter, either explicitly or by defaultsession
:verify
,cert
, orproxies
properties in your customsession
, then that value will be kept and the adapter's value will be ignored, even if you set it on the adapter explicitlyThe only case where this should cause breakage of existing code is where all of the following are true: