feat(client): allow configuring TLS verification#8
Merged
leo-altertable merged 1 commit intoaltertable-ai:mainfrom Apr 10, 2026
Merged
Conversation
leo-altertable
approved these changes
Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
verifyparameter toClient(...)and forward it to the underlyinghttpx.ClientFalseand anssl.SSLContextverify=Falsedevelopment use case in the READMEImpact analysis
altertable-lakehouse-pythonverifydefaults toTrueTests
pytestruff check .Cross-SDK check
altertable-ai/altertable-python: its client already exposes a transport-level option (timeout) but does not currently expose TLS verification controls, so this PR does not introduce an established cross-SDK inconsistency to mirror or unwindSpec alignment
Closes #7