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

Why use different keys to distinguish different applications? This could make downstream application configuration files difficult to maintain. #9935

New Issue
Closed
opened 2026-02-21 18:40:45 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:40:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @skys-mission on GitHub (Mar 8, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • 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.

As a downstream application, I usually prefer to write the key into the configuration file, while different functionalities might be hard-coded in the SDK I encapsulate. I tend to use grouped keys or a unique key to access all applications. Currently, using Dify, keys are used to distinguish different applications with the same API, which causes me a lot of trouble.
Could a new access mode be added to support using the same key with different APIs or using other interface parameters with the same key to control functionality?

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @skys-mission on GitHub (Mar 8, 2025). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [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. As a downstream application, I usually prefer to write the key into the configuration file, while different functionalities might be hard-coded in the SDK I encapsulate. I tend to use grouped keys or a unique key to access all applications. Currently, using Dify, keys are used to distinguish different applications with the same API, which causes me a lot of trouble. Could a new access mode be added to support using the same key with different APIs or using other interface parameters with the same key to control functionality? ### 2. Additional context or comments _No response_ ### 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 18:40:45 -05:00
yindo closed this issue 2026-02-21 18:40:45 -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#9935
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?