Support uploading to volumes in Bucket Explorer

[jmthomas]

What is the use case or problem this feature would solve?

Ability to upload files to volumes.

Additional context

Upload built on S3 presigned PUT. Not filesystem-capable.

Flow (BucketExplorer.vue:683-693):

1. Frontend ask backend for presigned URL → get_upload_presigned_request (storage_controller.rb:430)
2. axios PUT file direct to object store (versitygw) via that URL

get_upload_presigned_request hard-requires params.require(:bucket) and calls bucket.presigned_request. Presigned URL is a S3 concept only.

Volumes = host filesystem mounts (OPENC3_*_VOLUME env, storage_controller.rb:173). No S3. No presigned URL possible. Nothing to PUT to.

Volume upload need new backend endpoint: receive raw/multipart body, sanitize_path, write to /{volume}/{path} on filesystem (mirror download's volume branch), plus authorization('system_set') + RBAC.

Screenshots

No response

[crawlchat]

Thanks for the detailed write-up! Your analysis is accurate. This is a legitimate feature gap — the current upload flow is entirely S3/presigned-URL based and has no filesystem path for volumes.

Here's a structured summary of the work needed, based on your findings and the existing codebase patterns:

🔍 Root Cause Summary

The current upload flow (BucketExplorer.vue → storage_controller.rb#get_upload_presigned_request) is hardcoded to require a bucket param and calls bucket.presigned_request — an S3-only concept.

Volumes (OPENC3_*_VOLUME env vars) are host filesystem mounts with no S3 interface, so there's no presigned URL to generate and no object store to PUT to.

The download side already has a volume branch in storage_controller.rb (mirroring sanitize_path + direct file read), but upload has no equivalent.

🛠️ Required Changes

Backend (storage_controller.rb)

• Add a new endpoint (e.g., POST /storage/upload_volume) that:
  • Accepts multipart/form-data or raw body
  • Requires params[:volume] and params[:path]
  • Calls sanitize_path (mirroring the download branch)
  • Writes the file to /{volume}/{path} on the filesystem
  • Applies authorization('system_set') + appropriate RBAC

Frontend (BucketExplorer.vue)

• Detect when the current browser context is a volume (not a bucket)
• Instead of calling get_upload_presigned_request + axios PUT, call the new upload_volume endpoint directly with the file as multipart/form-data

❓ Questions for the Team

To help scope this properly, a few things would be useful to clarify:

1. Which volumes need upload support? All OPENC3_*_VOLUME mounts, or specific ones?
2. File size concerns? Since this goes through the web server (no presigned URL bypass), large file uploads will add load — is there a size limit needed?
3. Is there an existing multipart upload pattern elsewhere in the codebase? (e.g., gem upload) that could be reused for the backend receiver?

This is a well-scoped feature request. If the team wants to move forward, the pattern is clear — it mirrors the existing volume download branch but in reverse. Would be great to have a core contributor confirm the preferred endpoint shape before a PR is opened.