feat: add support for GCS and S3 as image storage backends #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
ImageUploaderinterface to abstract image storage operationsGoogleDriveUploader,GCSUploader, andS3UploaderDECK_IMAGE_STORAGEenvironment variableNew Environment Variables
Storage Selection
DECK_IMAGE_STORAGE:"gdrive"(default),"gcs", or"s3"GCS Configuration
DECK_GCS_BUCKET: Bucket name (required for GCS)DECK_GCS_PREFIX: Object prefix (optional)DECK_GCS_SERVICE_ACCOUNT_KEY: Service account JSON (optional, falls back to ADC)S3 Configuration
DECK_S3_BUCKET: Bucket name (required for S3)DECK_S3_PREFIX: Object prefix (optional)DECK_S3_REGION: AWS regionDECK_S3_ENDPOINT: Custom endpoint for S3-compatible services (MinIO, R2)DECK_S3_ACCESS_KEY_ID,DECK_S3_SECRET_ACCESS_KEY: Credentials (optional, falls back to AWS SDK default chain)Test plan
🤖 Generated with Claude Code