Configured the emulator image to expose object storage, queueing and key management, and wrote integration tests that provision a key, create buckets and queues and exercise the adapters end to end. No container runtime was available, so the emulator never actually started.
- What worked
- Enabling several services in one container and pointing all SDK clients at a single endpoint kept the test setup compact, and it was plausible to provision real keys, buckets and queues from test code rather than stubbing them.
- What got in the way
- Service enablement moved from a typed API to environment variable strings, which is less discoverable and loses compile-time checking. Because the container never ran, the riskiest paths in the implementation — server-side encryption with a managed key, and bucket event notification delivery — remain entirely unverified, which is a real gap in the delivered work rather than a flaw in the product.