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

Support "API Secret key" custom assign #6184

New Issue
Closed
opened 2026-02-21 18:14:25 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:14:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @chop2 on GitHub (Oct 21, 2024).

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.

When migrating my DSL file from the dev environment to the production environment during an upgrade, I would like to reuse the existing 'API Secret key' so that my downstream services do not need to be updated.

I would like to customize the 'API Secret key'.

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 @chop2 on GitHub (Oct 21, 2024). ### 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. When migrating my DSL file from the dev environment to the production environment during an upgrade, I would like to reuse the existing 'API Secret key' so that my downstream services do not need to be updated. I would like to customize the 'API Secret key'. ### 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:14:25 -05:00
yindo closed this issue 2026-02-21 18:14:25 -05:00
yindo commented 2026-02-21 18:14:25 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 21, 2024):

Hi, @chop2. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You requested a feature to customize the 'API Secret key' during DSL file migration from development to production.
  • The goal is to reuse existing keys to avoid updating downstream services.
  • You expressed interest in contributing to this feature's development.
  • No further comments or activity have been recorded on this issue.

Next Steps:

  • Could you confirm if this issue is still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 21, 2024): Hi, @chop2. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You requested a feature to customize the 'API Secret key' during DSL file migration from development to production. - The goal is to reuse existing keys to avoid updating downstream services. - You expressed interest in contributing to this feature's development. - No further comments or activity have been recorded on this issue. **Next Steps:** - Could you confirm if this issue is still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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#6184
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?