-
Notifications
You must be signed in to change notification settings - Fork 118
Implement Dagger Sandbox for the MCP #3940
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
Conversation
This reverts commit 1e9ee36.
9 failing tests:
Top 25 slowest tests (at least 2 minutes):
|
| databricks experimental apps-mcp --warehouse-id abc123 --docker-image node:20-alpine | ||
| # Start without containerized validation | ||
| databricks experimental apps-mcp --warehouse-id abc123 --use-dagger=false`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this the default mode?
| log.Info(ctx, "Checking MCP server environment") | ||
|
|
||
| // Check Databricks authentication | ||
| w := cmdctx.WorkspaceClient(ctx) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SDK template requires much more env vars in .env file - does it make sense to detect if there is SDK template installed and enforce checks for .env?
|
Closing for now. Might come back in a different shape later |
This reverts commit 1e9ee36.
Changes
Add a docker-based sandbox using dagger. Dagger is off be default and must be enabled explicitly by the user.
The dagger 3p lib is adding ~3MB to the CLI binary size.
Why
Tests