fix: plugin invoke request not support trigger and datasource plugins

[hjlarry]

Pull Request Checklist

fix plugin_runner.invoke not work for trigger and datasource plugins

error example: https://github.com/langgenius/dify-official-plugins/actions/runs/20295949196/job/58289586117?pr=2274

Compatibility Check

• I have checked whether this change affects the backward compatibility of the plugin declared in README.md
• I have checked whether this change affects the forward compatibility of the plugin declared in README.md
• If this change introduces a breaking change, I have discussed it with the project maintainer and specified the release version in the README.md
• I have described the compatibility impact and the corresponding version number in the PR description
• I have checked whether the plugin version is updated in the README.md

Available Checks

• Code has passed local tests
• Relevant documentation has been updated (if necessary)

[gemini-code-assist]

Summary of Changes

Hello @hjlarry, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical bug preventing the plugin_runner.invoke mechanism from properly supporting trigger and datasource plugins. By extending the PluginInvokeRequest's action field to include DatasourceActions and TriggerActions, the system can now correctly process invocation requests for these plugin categories, ensuring their seamless integration and functionality within the Dify plugin ecosystem.

Highlights

• Enhanced Plugin Invocation Support: The PluginInvokeRequest class has been updated to correctly handle DatasourceActions and TriggerActions, resolving a bug where plugin_runner.invoke previously failed for these specific plugin types.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request fixes an issue where plugin_runner.invoke did not support trigger and datasource plugins. The changes correctly add DatasourceActions and TriggerActions to the PluginInvokeRequest. I've added a couple of suggestions to make this even more robust by including other missing action types, which will help prevent similar issues in the future. Overall, this is a good and necessary fix.