Skip to content

Fix startup message and add connectivity check for S3 storage#57

Merged
andrew merged 2 commits intomainfrom
fix-s3-storage-startup-message
Apr 3, 2026
Merged

Fix startup message and add connectivity check for S3 storage#57
andrew merged 2 commits intomainfrom
fix-s3-storage-startup-message

Conversation

@andrew
Copy link
Copy Markdown
Contributor

@andrew andrew commented Apr 1, 2026

When S3 storage is configured, the startup log incorrectly showed the default local path (./cache/artifacts) instead of the actual S3 URL. The stats endpoint had the same problem.

This also adds a lightweight connectivity check at startup (an Exists call against the bucket) so bad credentials or unreachable endpoints fail immediately rather than on first request.

Fixes #49

When S3 storage is configured, the startup log incorrectly showed the
default local path (./cache/artifacts) instead of the actual S3 URL.
This also adds a lightweight connectivity check at startup so bad
credentials or endpoints fail immediately rather than on first request.

Add URL() and Close() to the Storage interface so all backends report
their URL and can be cleaned up properly. Rename the stats JSON field
from storage_path to storage_url. Close storage in error paths and
during graceful shutdown.

Fixes #49
@andrew andrew force-pushed the fix-s3-storage-startup-message branch from 6ce79b0 to 071400b Compare April 2, 2026 17:12
OpenBucket normalizes Windows paths to file:///C:/path (three slashes)
but the test expected file://C:/path (two slashes).
@andrew andrew merged commit beddf83 into main Apr 3, 2026
5 checks passed
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.

S3 storage mode - startup message doesn't indicate that S3 mode is enabled

1 participant