Skip to content

feat(client): allow configuring TLS verification#8

Merged
leo-altertable merged 1 commit intoaltertable-ai:mainfrom
albert20260301:fix/7-client-verify
Apr 10, 2026
Merged

feat(client): allow configuring TLS verification#8
leo-altertable merged 1 commit intoaltertable-ai:mainfrom
albert20260301:fix/7-client-verify

Conversation

@albert20260301
Copy link
Copy Markdown
Contributor

Summary

  • add a verify parameter to Client(...) and forward it to the underlying httpx.Client
  • cover both supported cases requested in the issue: False and an ssl.SSLContext
  • document the verify=False development use case in the README
  • make the existing Docker test fixture store the mapped port as a string so the suite runs cleanly on Python 3.14

Impact analysis

  • affects only Python SDK client initialization in altertable-lakehouse-python
  • default behavior is unchanged because verify defaults to True
  • unblocks local and custom CA / self-signed TLS setups without changing request semantics for existing users

Tests

  • pytest
  • ruff check .

Cross-SDK check

  • checked 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 unwind

Spec alignment

  • this is a client transport configuration surface, not a spec-defined API field, so there is no request/response spec divergence

Closes #7

@leo-altertable leo-altertable merged commit 0356ca3 into altertable-ai:main Apr 10, 2026
8 checks passed
@albert20260301 albert20260301 deleted the fix/7-client-verify branch April 10, 2026 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow specifying additional SSL parameters when instantiating a Client

2 participants