langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

[PR #1448] [CLOSED] feat(gemini_cf): add Gemini via Cloudflare Worker provider #1898

New Issue
Closed
opened 2026-02-16 10:24:20 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 10:24:20 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-official-plugins/pull/1448
Author: @cherish156-wang
Created: 8/7/2025
Status: ❌ Closed

Base: main ← Head: feature/gemini-cf-provider

📝 Commits (3)

  • 9e2553c feat(gemini_cf): add Gemini via Cloudflare Worker provider with 2.5/2.0 LLM models and credentials (base_url, api_key)
  • 1aef3e8 chore(gemini_cf): align manifest to plugin schema; add provider schema and _position.yaml
  • 0e9a5a3 chore(gemini_cf): add icon_s_en.svg placeholder for packaging

📊 Changes

9 files changed (+203 additions, -0 deletions)

View changed files

➕ models/gemini_cf/README.md (+14 -0)
➕ models/gemini_cf/icon_s_en.svg (+1 -0)
➕ models/gemini_cf/manifest.yaml (+38 -0)
➕ models/gemini_cf/models/llm/_position.yaml (+4 -0)
➕ models/gemini_cf/models/llm/gemini-2.0-flash.yaml (+26 -0)
➕ models/gemini_cf/models/llm/gemini-2.5-flash-lite.yaml (+26 -0)
➕ models/gemini_cf/models/llm/gemini-2.5-flash.yaml (+26 -0)
➕ models/gemini_cf/models/llm/gemini-2.5-pro.yaml (+26 -0)
➕ models/gemini_cf/provider/gemini_cf.yaml (+42 -0)

📄 Description

This PR adds a new provider 'gemini_cf' to access Google Gemini via Cloudflare Worker reverse proxy.\n\n- Provider manifest with credentials: base_url, api_key (sent as x-api-key)\n- LLM models: gemini-2.5-pro, gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.0-flash\n- README for configuration guidance\n\nIf maintainers prefer reusing existing google_gemini or openai_compatible providers instead of a new provider folder, I can migrate these YAMLs accordingly.\n

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-official-plugins/pull/1448 **Author:** [@cherish156-wang](https://github.com/cherish156-wang) **Created:** 8/7/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feature/gemini-cf-provider` --- ### 📝 Commits (3) - [`9e2553c`](https://github.com/langgenius/dify-official-plugins/commit/9e2553c8270cf53d2d79666ce7db18a67c6c7aa8) feat(gemini_cf): add Gemini via Cloudflare Worker provider with 2.5/2.0 LLM models and credentials (base_url, api_key) - [`1aef3e8`](https://github.com/langgenius/dify-official-plugins/commit/1aef3e8a7d02143dceb540651df1d59729f4e9fb) chore(gemini_cf): align manifest to plugin schema; add provider schema and _position.yaml - [`0e9a5a3`](https://github.com/langgenius/dify-official-plugins/commit/0e9a5a37b7c6916c37f91d0c870d027a3bbac4d4) chore(gemini_cf): add icon_s_en.svg placeholder for packaging ### 📊 Changes **9 files changed** (+203 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `models/gemini_cf/README.md` (+14 -0) ➕ `models/gemini_cf/icon_s_en.svg` (+1 -0) ➕ `models/gemini_cf/manifest.yaml` (+38 -0) ➕ `models/gemini_cf/models/llm/_position.yaml` (+4 -0) ➕ `models/gemini_cf/models/llm/gemini-2.0-flash.yaml` (+26 -0) ➕ `models/gemini_cf/models/llm/gemini-2.5-flash-lite.yaml` (+26 -0) ➕ `models/gemini_cf/models/llm/gemini-2.5-flash.yaml` (+26 -0) ➕ `models/gemini_cf/models/llm/gemini-2.5-pro.yaml` (+26 -0) ➕ `models/gemini_cf/provider/gemini_cf.yaml` (+42 -0) </details> ### 📄 Description This PR adds a new provider 'gemini_cf' to access Google Gemini via Cloudflare Worker reverse proxy.\n\n- Provider manifest with credentials: base_url, api_key (sent as x-api-key)\n- LLM models: gemini-2.5-pro, gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.0-flash\n- README for configuration guidance\n\nIf maintainers prefer reusing existing google_gemini or openai_compatible providers instead of a new provider folder, I can migrate these YAMLs accordingly.\n --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 10:24:20 -05:00
yindo closed this issue 2026-02-16 10:24:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#1898
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?