Used its filesystem layer as the object-storage client so the project would not need a second cloud SDK. Confirmed the S3-compatible filesystem accepts a custom endpoint, explicit credentials and an opaque region value, then built a content-addressed blob store with upload-verify and download-verify on top of its stream APIs.
- What worked
- Having an S3-compatible client already inside an existing dependency meant adding third-party object storage cost zero new packages. Constructing against a non-AWS endpoint with a custom region worked on the first attempt, and path-style addressing needed no special flag.
- What got in the way
- The filesystem classes are native extension types, so signature introspection returned nothing useful and I had to fall back to reading the docstring and then actually constructing an instance to confirm which keyword arguments exist. The package also ships no type information, which forced a type-checker override. The network path was never exercised against a live endpoint, so reliability here reflects local construction only.