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

[PR #11346] Add aliyun builtin tools #27180

New Issue
Closed
opened 2026-02-21 20:41:01 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:41:01 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/11346

State: closed
Merged: No

Summary

If developers have deployed some model service on Aliyun (Alibaba Cloud), for example, Aliyun PAI EAS , and they want to call the service on dify. Or I will directly call Aliyun bailian API.

Tip

Close issue syntax: Resolves #11323, see documentation for more details.

Screenshots

image
image
image
image

Before: After:
... ...

Checklist

Important

Please review the checklist below before submitting your pull request.

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/11346 **State:** closed **Merged:** No --- # Summary If developers have deployed some model service on Aliyun (Alibaba Cloud), for example, [Aliyun PAI EAS ](https://help.aliyun.com/zh/pai/user-guide/overview-2), and they want to call the service on dify. Or I will directly call [Aliyun bailian](https://bailian.console.aliyun.com/#/home) API. > [!Tip] > Close issue syntax: `Resolves #11323`, see [documentation](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) for more details. # Screenshots ![image](https://github.com/user-attachments/assets/eadb41dd-79d1-4e55-9e38-ecbd2678ba25) ![image](https://github.com/user-attachments/assets/c196da3c-a10e-495f-83c7-b2458dcf240f) ![image](https://github.com/user-attachments/assets/84df0fc1-8ccc-4705-b5c3-746ff9356ecd) ![image](https://github.com/user-attachments/assets/29928f13-51cb-437a-acf7-685eaacb8779) <table> <tr> <td>Before: </td> <td>After: </td> </tr> <tr> <td>...</td> <td>...</td> </tr> </table> # Checklist > [!IMPORTANT] > Please review the checklist below before submitting your pull request. - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [X] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [X] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [X] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:41:01 -05:00
yindo closed this issue 2026-02-21 20:41:01 -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 pull-request
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#27180
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?