You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The README notes that connector support for Volumes is in progress. We'd like to
contribute a minimal Python client for the Volumes API as a reference for other
implementors working with the protocol.
Scope
A lightweight, dependency-minimal client that:
Loads a credential profile (.share JSON file)
Discovers shares, schemas, and volumes via the REST API
Calls temporary-volume-credentials and returns usable cloud credentials
Includes a CLI entry point for quick E2E validation
No framework dependencies beyond requests and standard library.
Questions before contributing
Should this live in the existing delta-sharing Python package or as a standalone?
Any preferred conventions for the client API surface (e.g., sync-only, class-based)?
Where in the repo structure would a community connector belong?
Hi Yoshiki, thanks for submitting this. We definitely want to add volume support on the client side. We are taking a look at your questions and will get back to you shortly on how best to contribute this PR.
Activity
Akramio commentedon Jul 20, 2026
Hi Yoshiki, thanks for submitting this. We definitely want to add volume support on the client side. We are taking a look at your questions and will get back to you shortly on how best to contribute this PR.
littlegrasscao commentedon Nov 18, 2026
Hi @Yoshiki0705 , thanks for opening the issue. To clarify, this is just a documentation update, right?
The volume ARN and IAM are owned by catalog. OpenSharing only knows storage location and name.
The user needs to create a IAM role with correct policy in S3, then import the IAM in catalog, and link to the storage location.
Feel free to send a PR for updates.