langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #4266] feat: Add storage type and Google Storage settings to worker #24464

New Issue
Closed
opened 2026-02-21 20:23:03 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:23:03 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/4266

State: closed
Merged: Yes

Description

This change adds support for using Google Cloud Storage as the storage backend for user files in Dify. It introduces two new environment variables for configuring Google Storage: GOOGLE_STORAGE_BUCKET_NAME and GOOGLE_STORAGE_SERVICE_ACCOUNT_JSON_BASE64. When STORAGE_TYPE is set to google-storage, these variables will be used to connect to and store files in a Google Storage bucket.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update, included: Dify Document
  • Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement
  • Dependency upgrade

How Has This Been Tested?

  • Tested setting STORAGE_TYPE=google-storage and providing valid values for GOOGLE_STORAGE_BUCKET_NAME and GOOGLE_STORAGE_SERVICE_ACCOUNT_JSON_BASE64
  • Verified user files are successfully stored in and retrieved from the configured Google Storage bucket
  • Ensured existing storage backends (local, S3, Azure Blob) continue to function as expected

Suggested Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
**Original Pull Request:** https://github.com/langgenius/dify/pull/4266 **State:** closed **Merged:** Yes --- # Description This change adds support for using Google Cloud Storage as the storage backend for user files in Dify. It introduces two new environment variables for configuring Google Storage: `GOOGLE_STORAGE_BUCKET_NAME` and `GOOGLE_STORAGE_SERVICE_ACCOUNT_JSON_BASE64`. When `STORAGE_TYPE` is set to `google-storage`, these variables will be used to connect to and store files in a Google Storage bucket. ## Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [ ] Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement - [ ] Dependency upgrade # How Has This Been Tested? - [ ] Tested setting `STORAGE_TYPE=google-storage` and providing valid values for `GOOGLE_STORAGE_BUCKET_NAME` and `GOOGLE_STORAGE_SERVICE_ACCOUNT_JSON_BASE64` - [ ] Verified user files are successfully stored in and retrieved from the configured Google Storage bucket - [ ] Ensured existing storage backends (local, S3, Azure Blob) continue to function as expected # Suggested Checklist: - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [x] My changes generate no new warnings - [ ] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes
yindo added the pull-request label 2026-02-21 20:23:03 -05:00
yindo closed this issue 2026-02-21 20:23:03 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#24464
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?