dify - 💡(How to fix) Fix [Feature Request] Add API endpoint to retrieve current workflow_id or include it in Application Info

TL;DR

To address the issue of retrieving the latest workflow_id without triggering the workflow, consider adding a new API endpoint or updating the existing /info API to include the currently published workflow_id.

Guidance

• Investigate the feasibility of introducing a new API endpoint dedicated to retrieving the current workflow_id, considering the potential impact on the existing API structure and documentation.
• Explore the possibility of updating the existing /info API to include the workflow_id of the currently published version, ensuring backward compatibility and minimal disruption to current users.
• Evaluate the trade-offs between these two approaches, including factors such as development effort, performance, and security implications.
• Consider engaging with the development team to discuss the proposed solutions and gather feedback on the best course of action.

Example

No code snippet is provided as the issue focuses on API design and functionality rather than specific code implementation.

Notes

The solution will depend on the specific requirements and constraints of the Dify project, including the existing API architecture, security considerations, and user expectations. It is essential to carefully evaluate the proposed solutions to ensure they align with the project's goals and standards.

Recommendation

Apply a workaround by introducing a new API endpoint dedicated to retrieving the current workflow_id, as this approach may offer more flexibility and scalability for future developments.