Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[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.
Currently, a workflow or advanced-chat type application would be able to trigger draft version test before publishing the changes to end users. However, non-workflow type application did NOT support this feature, e.g. chat completion or agent chat type application.
Besides, the current versioning features seems like very simple and might not be suitable for enterprise production usage. There are two pain points:
lack of change commit message of each version, which means we can NOT know each version change by one line message;
lack of change diff or changed blocks / nodes diff show, which means we can NOT make sure it's expected change and release to production while we click "publish"
2. Additional context or comments
Without some required changes for the version mgmt and release mgmt, I'm afraid that it might be risky to open the access for end users on production environment dify site. A good example that we can learn from is Apollo config center, it has implemented cross environment config sync and also gray deployment before the version goes live: https://www.apolloconfig.com/#/en/README?id=features
Do we have a roadmap for enhancing the version mgmt and release mgmt ?
Thanks.
3. Can you help us with this feature?
[ ] I am interested in contributing to this feature.
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Currently, a workflow or advanced-chat type application would be able to trigger draft version test before publishing the changes to end users. However, non-workflow type application did NOT support this feature, e.g. chat completion or agent chat type application.
Besides, the current versioning features seems like very simple and might not be suitable for enterprise production usage. There are two pain points:
2. Additional context or comments
Without some required changes for the version mgmt and release mgmt, I'm afraid that it might be risky to open the access for end users on production environment dify site. A good example that we can learn from is Apollo config center, it has implemented cross environment config sync and also gray deployment before the version goes live: https://www.apolloconfig.com/#/en/README?id=features
Do we have a roadmap for enhancing the version mgmt and release mgmt ? Thanks.
3. Can you help us with this feature?