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

Inconsistency in AI Proxy plugin configuration for Mistral #7609

Closed
2 tasks done
lfavreli opened this issue Jul 2, 2024 · 0 comments · Fixed by #7677
Closed
2 tasks done

Inconsistency in AI Proxy plugin configuration for Mistral #7609

lfavreli opened this issue Jul 2, 2024 · 0 comments · Fixed by #7677
Assignees

Comments

@lfavreli
Copy link

lfavreli commented Jul 2, 2024

Where is the problem?

https://docs.konghq.com/hub/kong-inc/ai-proxy/how-to/llm-provider-integration-guides/mistral/

What happened?

There is an inconsistency between the documentation and the provided cURL command for configuring the AI Proxy plugin for Mistral. The documentation states:

Enable and configure the AI Proxy plugin for Mistral (using ollama format in this example):"

However, the command uses the openai format instead of ollama:

curl -X POST http://localhost:8001/routes/mistral-chat/plugins \
 --data "name=ai-proxy" \
 --data "config.route_type=llm/v1/chat" \
 --data "config.auth.header_name=Authorization" \
 --data "config.auth.header_value=Bearer <MISTRAL_AI_KEY>" \
 --data "config.model.provider=mistral" \
 --data "config.model.name=mistral-tiny" \
 --data "config.model.options.mistral_format=openai" \
 --data "config.model.options.upstream_url=https://api.mistral.ai/v1/chat/completions" \ 

This discrepancy can lead to confusion.

What did you expect to happen?

The documentation should correctly reflect the format used in the command.

If the format openai is correct, the documentation should state:

"Enable and configure the AI Proxy plugin for Mistral (using openai format in this example):".

If ollama is correct, the command should be updated accordingly.

Code of Conduct and Community Expectations

  • I agree to follow this project's Code of Conduct
  • I agree to abide by the Community Expectations
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 a pull request may close this issue.

2 participants