-
Notifications
You must be signed in to change notification settings - Fork 424
452Remove-Integration-Type #678
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
452Remove-Integration-Type #678
Conversation
PR Review: Remove MCP Integration Type (#678)SummaryThis PR removes "MCP" as an integration type option from the admin UI and API, keeping only "REST" as the supported integration type. This aligns with the requirement that MCP servers are supported under a separate "Gateways" section. Changes Reviewed1. Schema Changes (
|
Signed-off-by: NAYANAR <[email protected]>
Signed-off-by: NAYANAR <[email protected]>
- Update ToolCreate and ToolUpdate validation to only accept REST integration type - Fix test cases that still referenced MCP integration type - Update mock return values and assertions in test files - Ensure all doctests pass with REST-only validation - Maintain full test suite compatibility All tests now pass: 1307 passed, 10 skipped
5645ef6 to
6784fe5
Compare
|
Will be reverting this through a separate PR. |
* Remove Integration Type: MCP Signed-off-by: NAYANAR <[email protected]> * testcase fixed Signed-off-by: NAYANAR <[email protected]> * Fix validation logic and tests after MCP integration type removal - Update ToolCreate and ToolUpdate validation to only accept REST integration type - Fix test cases that still referenced MCP integration type - Update mock return values and assertions in test files - Ensure all doctests pass with REST-only validation - Maintain full test suite compatibility All tests now pass: 1307 passed, 10 skipped --------- Signed-off-by: NAYANAR <[email protected]> Co-authored-by: NAYANAR <[email protected]> Co-authored-by: Mihai Criveti <[email protected]>
* Remove Integration Type: MCP Signed-off-by: NAYANAR <[email protected]> * testcase fixed Signed-off-by: NAYANAR <[email protected]> * Fix validation logic and tests after MCP integration type removal - Update ToolCreate and ToolUpdate validation to only accept REST integration type - Fix test cases that still referenced MCP integration type - Update mock return values and assertions in test files - Ensure all doctests pass with REST-only validation - Maintain full test suite compatibility All tests now pass: 1307 passed, 10 skipped --------- Signed-off-by: NAYANAR <[email protected]> Co-authored-by: NAYANAR <[email protected]> Co-authored-by: Mihai Criveti <[email protected]>
* Remove Integration Type: MCP Signed-off-by: NAYANAR <[email protected]> * testcase fixed Signed-off-by: NAYANAR <[email protected]> * Fix validation logic and tests after MCP integration type removal - Update ToolCreate and ToolUpdate validation to only accept REST integration type - Fix test cases that still referenced MCP integration type - Update mock return values and assertions in test files - Ensure all doctests pass with REST-only validation - Maintain full test suite compatibility All tests now pass: 1307 passed, 10 skipped --------- Signed-off-by: NAYANAR <[email protected]> Co-authored-by: NAYANAR <[email protected]> Co-authored-by: Mihai Criveti <[email protected]>
📌 Summary
What problem does this PR fix and why?
integrationType should only support REST, not MCP closes #452
💡 Fix Description
How did you solve it? Key design points.
The integrationType field in the admin UI (and API) currently allows "MCP", but this is not desired. The issue requests removing "MCP" from all input forms (modals)—keeping only "REST". There’s mention that support for "MCP" servers may eventually be added under a separate "Gateways" section.
🧪 Verification
make lintmake test📐 MCP Compliance (if relevant)
✅ Checklist
make black isort pre-commit)