fix(#92): Add support for env HTTP_REQUEST_SSL_VERIFY

[Oscaner]

Pull Request Checklist

Thank you for your contribution! Before submitting your PR, please make sure you have completed the following checks:

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 @Oscaner, 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 issue #92 by enhancing the plugin's HTTP request handling capabilities. It introduces a configurable option to control SSL certificate verification, providing greater flexibility for environments that may require custom SSL settings or need to bypass verification for specific scenarios. This change ensures that the plugin can adapt to diverse network configurations while maintaining security best practices by defaulting to enabled SSL verification.

Highlights

• New Configuration Option: Introduced a new environment variable, HTTP_REQUEST_SSL_VERIFY, within the DifyPluginEnv configuration. This boolean field, defaulting to True, allows users to enable or disable SSL certificate verification for HTTP requests made by the plugin.
• SSL Verification Integration: Integrated the newly added HTTP_REQUEST_SSL_VERIFY setting into the file.py module. HTTP requests made using httpx.get to fetch file blobs will now respect this configuration, allowing for flexible control over SSL verification.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 introduces a new environment variable HTTP_REQUEST_SSL_VERIFY to control SSL certificate verification for HTTP requests, which is a valuable addition for development and testing environments. The implementation is straightforward, but I've identified a potential issue with how the configuration is loaded in python/dify_plugin/file/file.py. Instantiating the configuration at the module level can lead to stale configuration values and make testing more difficult. I've provided suggestions to refactor this to a just-in-time instantiation pattern, which is more robust.

[gemini-code-assist]

Instantiating DifyPluginEnv at the module level can lead to issues with testability and configuration reloading. The configuration is loaded only once when the module is first imported. If environment variables are changed at runtime (e.g., in tests), this object will not reflect the new values. It's better to remove this module-level instance and create it just-in-time where it's needed (inside the blob method).

[gemini-code-assist]

To avoid using a module-level configuration object and ensure the latest settings are always used, you can instantiate DifyPluginEnv directly in this call. This improves testability and makes the dependency explicit.

Suggested change

	response = httpx.get(self.url, verify=_plugin_config.HTTP_REQUEST_SSL_VERIFY)
	response = httpx.get(self.url, verify=DifyPluginEnv().HTTP_REQUEST_SSL_VERIFY)