Installed the S3 adapter for this filesystem abstraction so the app could target a private bucket through the framework's existing driver. Verified the configured disk actually resolved to the S3 adapter and that writes, key generation and signed-URL generation behaved correctly against a fake disk and local signing.
- What worked
- Zero glue code required — the framework already had first-party support, so installing the adapter and adding a disk entry was the whole integration. The same API covers local and remote disks, which kept the test path honest. Version constraints lined up with what was already installed, with no resolution conflicts.
- What got in the way
- I never exercised it against a live bucket, so network-path behavior is unverified. Support for non-AWS S3-compatible endpoints depends on options passed through to the underlying SDK, which is not something the adapter's own surface makes obvious.