Skip to content

fix(storage): improve robustness of cloud storage operations#890

Closed
filiperochalopes wants to merge 2 commits into
OpenConceptLab:masterfrom
filiperochalopes:fix/local-rustfs-export-run-with-aws-s3-compatibility
Closed

fix(storage): improve robustness of cloud storage operations#890
filiperochalopes wants to merge 2 commits into
OpenConceptLab:masterfrom
filiperochalopes:fix/local-rustfs-export-run-with-aws-s3-compatibility

Conversation

@filiperochalopes

@filiperochalopes filiperochalopes commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

I did it so rustfs and oclweb2 can run seamless with export tests locally @snyaggarwal

  • Make key fetching deterministic for S3-compatible stores by improving sorting logic and handling objects that lack standard metadata

  • Add robust error handling to AWS S3 lookups to gracefully handle missing credentials or failed API calls

  • Update development configuration defaults for consistent use of local MinIO/RustFS endpoint settings

***

* Make key fetching deterministic for S3-compatible stores by improving sorting logic and handling objects that lack standard metadata

* Add robust error handling to AWS S3 lookups to gracefully handle missing credentials or failed API calls

* Update development configuration defaults for consistent use of local MinIO/RustFS endpoint settings

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b5eda51222

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docker-compose.yml Outdated
- MINIO_SECRET_KEY
- MINIO_SECURE
# Export storage defaults to host-published local RustFS/MinIO-compatible storage.
- EXPORT_SERVICE=${EXPORT_SERVICE-core.services.storages.cloud.minio.MinIO}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the compose default on the configured S3 backend

When docker-compose.yml is used without an explicit EXPORT_SERVICE, this line now injects core.services.storages.cloud.minio.MinIO into the API container, overriding the application default in core/settings.py of core.services.storages.cloud.aws.S3. In production-style compose deployments that already provide AWS credentials/bucket but have never set EXPORT_SERVICE, exports and downloads will now try to initialize MinIO against host.docker.internal:${MINIO_PORT:-9090} instead of S3, and the base compose file does not start a RustFS/MinIO service. This should stay opt-in for the local MinIO setup rather than changing the default backend for every compose run.

Useful? React with 👍 / 👎.

@filiperochalopes filiperochalopes marked this pull request as draft July 8, 2026 15:06
* Remove redundant MinIO service configurations from local docker-compose setup

* Refine cloud storage tests by removing specific integrity and permission checks
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.

1 participant