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

Add config to disable dataset ID encryption for cross-environment DSL import #16695

New Issue
Closed
opened 2026-02-21 19:27:13 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:27:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @kenwoodjw on GitHub (Sep 3, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Problem

When importing DSL files across different environments different tenant_id, knowledge bases are lost,
because dataset IDs are encrypted with the source environment's tenant_id,
but decrypted with the target environment's tenant_id.

Solution

Add a new configuration ENABLE_ENCRYPT_DATASET_ID to
control dataset ID encryption in DSL export/import.

2. Additional context or comments

Changes

  • Add DSL_EXPORT_ENCRYPT_DATASET_ID config (default:
    true)
  • When false, dataset IDs are stored as plain text
    in DSL
  • Backward compatible: supports both encrypted and
    plain text dataset IDs

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @kenwoodjw on GitHub (Sep 3, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. ## Problem When importing DSL files across different environments different tenant_id, knowledge bases are lost, because dataset IDs are encrypted with the source environment's tenant_id, but decrypted with the target environment's tenant_id. ## Solution Add a new configuration `ENABLE_ENCRYPT_DATASET_ID` to control dataset ID encryption in DSL export/import. ### 2. Additional context or comments ## Changes - Add `DSL_EXPORT_ENCRYPT_DATASET_ID` config (default: `true`) - When `false`, dataset IDs are stored as plain text in DSL - Backward compatible: supports both encrypted and plain text dataset IDs ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 19:27:13 -05:00
yindo closed this issue 2026-02-21 19:27:13 -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 💪 enhancement
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#16695
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?