Skip to content

Better logging for storage actions #3497

Description

@aarqon

Is your feature request related to a problem? Please describe.

I have been trying to diagnose a problem with decomposeds3 not connecting to a bucket and so far I have not found positive evidence of either errors in the configuration or that data has been moved to/changed in the bucket in question. The bucket management page (Backblaze B2 in this case) never registers a change in either case. Despite that I have no local data directories specified in my .env nor any files appearing in my bucket, files are persisting across restarts of the containers. There is no indication of where these files are being stored.

Describe the solution you'd like

It would be nice if I got confirmation of the data directory being used, whether s3 is being invoked, and if so whether it has successfully connected to the bucket in question. Any errors found along the way would also be nice to catch.

Describe alternatives you've considered

I have brought this up previously as an opencloud-compose issue, thinking it was an issue with my .env or some quirk of B2 keys, but without more information it's difficult to make progress.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions