[services] strip services route prefix in Go runtime#15120
Conversation
🦋 Changeset detectedLatest commit: f8a54d2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📦 CLI Tarball ReadyThe Vercel CLI tarball for this PR is now available! Quick TestYou can test this PR's CLI directly by running: npx https://vercel-g8y127hrv.vercel.sh/tarballs/vercel.tgz --helpUse in vercel.jsonTo use this CLI version in your project builds, add to your {
"build": {
"env": {
"VERCEL_CLI_VERSION": "vercel@https://vercel-g8y127hrv.vercel.sh/tarballs/vercel.tgz"
}
}
}Python Runtime WheelA Python runtime wheel was also built for this PR. |
🧪 Unit Test StrategyComparing: Strategy: Affected packages only ✅ Only testing packages that have been modified or depend on modified packages. Affected packages - 4 (10%)
Unaffected packages - 36 (90%)
Results
This comment is automatically generated based on the affected testing strategy |
b99226a to
4366a86
Compare
Adds support for automatically mounting user's Go server when running in zero config multi-service projects so that the app receives just
/pinginstead of/_/backend/pingDoes so by stripping the service route prefix in the reverse proxy before forwarding the request to the user app
Also introduces
vc-init-dev.goa dev server for the standalone server mode (as opposed to the legacy go-bridge handler mode) which does the same route prefix stripping.Adds
vc-utils.gofor shared utilities betweenvc-init.goandvc-init-dev.goNote
Low Risk Change
This PR adds e2e test fixtures and Go runtime infrastructure for stripping service route prefixes, containing no security-sensitive changes like auth, permissions, or data handling.
Risk assessment for commit f8a54d2.