Fix large payload tester mount isolation - remove test data from gateway #733
+47
−24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The large-payload-tester workflow had
/tmp/mcp-test-fs(test data) mounted to the gateway container, breaking test isolation. The gateway should only access test files through the filesystem MCP server via protocol, not direct filesystem access.Changes
/tmp/jq-payloads(payload dir) mounted, not/tmp/mcp-test-fs(test data)/tmp/jq-payloadson-demand viaMkdirAllwhen storing first payloadTechnical Detail
Gateway uses Docker-in-Docker (socket mounted). When launching backend MCP servers:
# Gateway executes this command (runs on host Docker daemon) docker run -v /tmp/mcp-test-fs:/workspace/test-data filesystem-mcp-serverThe path
/tmp/mcp-test-fsis relative to the host filesystem, not the gateway container's filesystem. Gateway container doesn't need this directory mounted to pass it to child containers.Result
Test data isolation ensures the gateway must retrieve files via MCP protocol, properly testing payload interception and storage.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.