Skip to content

fix(providers): probe dify key validation via chat-messages endpoint (#11002) - #11057

Closed
rqzbeh wants to merge 3 commits into
diegosouzapw:release/v3.8.50from
rqzbeh:fix/dify-validation-probe-endpoint
Closed

rqzbeh wants to merge 3 commits into
diegosouzapw:release/v3.8.50from
rqzbeh:fix/dify-validation-probe-endpoint

Conversation

@rqzbeh

@rqzbeh rqzbeh commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Fixes #11002 by adding a dedicated Dify key validator probing POST /v1/chat-messages and updating Dify's registry baseUrl.

@rqzbeh
rqzbeh requested a review from diegosouzapw as a code owner August 21, 2026 22:42
@diegosouzapw

Copy link
Copy Markdown
Owner

Fechando com crédito: o valor desta PR já foi entregue pela #11065 (mergeada para release/v3.8.50, memo pelo mesmo issue #11002). O validator Dify dedicado via /v1/chat-messages já existe no tip em:

  • src/lib/providers/validation/dify.ts (validateDifyProvider + resolveDifyChatMessagesUrl)
  • dispatch dify: validateDifyProvider em src/lib/providers/validation.ts
  • open-sse/config/providers/registry/dify/index.ts com baseUrl https://api.dify.ai

Sobre os deltas não subsumidos daqui: o baseUrl /v1 proposto seria inconsistente (o validator compõe {base}/v1/chat-messages ele mesmo, então manter a base sem /v1 é o correto); os toques em readyz/terminal-status/account-rotation parecem resíduo de branch antigo, não relacionados ao escopo dify. Obrigado pelo trabalho — a abordagem de probe foi exatamente a direção certa (#11065 usa o mesmo endpoint).

@diegosouzapw

Copy link
Copy Markdown
Owner

Subsumida por #11065 conforme explicado acima; obrigado pela contribuição.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(providers): dify key check always fails - validator probes /v1/chat/completions but Dify only serves /v1/chat-messages

2 participants