Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advanced Tool Intergration is different from version 0.15.3 #14300

Open
4 tasks done
liangnet opened this issue Feb 25, 2025 · 1 comment
Open
4 tasks done

Advanced Tool Intergration is different from version 0.15.3 #14300

liangnet opened this issue Feb 25, 2025 · 1 comment
Labels
📚 documentation Improvements or additions to documentation

Comments

@liangnet
Copy link

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Provide a description of requested docs changes

I pulled the latest version 0.15.3 and I found a difference point about path, they are
in document,
Image

in code,
Image

in version 0.15.0, I implemented a tool and located at core/tools/provider/builtin and run this tool successfully. However, after pulling the version 0.15.3, docker log showed many errors ad I saw the different directory structure. In order to find out what happened, I pull a clean one 0.15.3 and also see the Built-in tools such as

Image

So, I search the relevant words such as label and human_description, BUT! no one can be found.

@dosubot dosubot bot added the 📚 documentation Improvements or additions to documentation label Feb 25, 2025
Copy link

dosubot bot commented Feb 25, 2025

In version 0.15.3 of Dify, the directory structure for tool integration has changed. The YAML configuration files for tool integration are now located in the core/tools/provider/builtin directory. For example, if you are integrating a tool like GoogleSearch, you would create a google module (folder) under this directory and then create a google.yaml file within it. This YAML file should include the tool provider's basic information, such as the provider's name, icon, author, and other details necessary for frontend display [1].

Additionally, the built-in tools are organized under a "providers" directory, with each provider having its own subdirectory containing a "tools" directory. The tool configurations are stored as YAML files within these directories [2].

If you are encountering errors after updating to version 0.15.3, it might be due to these changes in the directory structure. You may need to adjust the location of your custom tool files to align with the new structure.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📚 documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant