Skip to content

0.22.3: the manifest read resolves S3 options from the environment - #175

Merged
nhobin219 merged 1 commit into
release/0.22.xfrom
fix/manifest-read-env-options
Oct 20, 2026
Merged

nhobin219 merged 1 commit into
release/0.22.xfrom
fix/manifest-read-env-options

Conversation

@nhobin219

Copy link
Copy Markdown
Owner

0.22.1's _counted_from_manifests gave pyiceberg {} when a reader passed no s3_options, instead of S3Options().resolved() as litelink does, so an endpoint set only in the environment (AWS_ENDPOINT_URL) never reached it and the open asked AWS (ACCESS_DENIED). Caught by agent-office's end-to-end test on its 0.7.2 build (agents read with no explicit options there).

New test: an S3 table opened with no options, the endpoint and key only in the environment, against rustfs: fails before with the e2e's exact error, passes after. published, reopen_credentials, snapshot_readers, catchup_pages with S3 required: 47 passed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PXyESUWnfYF3jXPHp7pz12

…nment

0.22.1 passed pyiceberg no properties when a reader gave no s3_options, so a
non-AWS endpoint in the environment never reached it (ACCESS_DENIED). Found by
agent-office's end-to-end office test on its 0.7.2 build.

build: 0.22.3

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PXyESUWnfYF3jXPHp7pz12
@nhobin219
nhobin219 merged commit a3f859f into release/0.22.x Oct 20, 2026
6 checks passed
@nhobin219
nhobin219 deleted the fix/manifest-read-env-options branch October 20, 2026 16:31
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.

1 participant