Skip to content

feat(isolation): add serviceGateways kit vocabulary #416

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.

Sign up for GitHub

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

Open
mogul wants to merge 5 commits into
base: main
Choose a base branch
from
Open

feat(isolation): add serviceGateways kit vocabulary #416

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3d20ab3
docs(isolation): add service gateways vocabulary ADR
mogul Sep 15, 2026
f498be8
feat(isolation): add service gateways vocabulary
mogul Sep 15, 2026
33a8242
fix(isolation): harden service gateway validation
mogul Oct 1, 2026
48eda7d
fix(isolation): close service gateway Compose bypasses
mogul Oct 8, 2026
04f4f21
fix(isolation): validate privileged lifecycle hooks
mogul Oct 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions integrations/isolation/acq-kits/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,18 @@ vocabulary:
backend maps these onto its native env mechanism (sbx `environment.variables`;
msb `--env NAME=value`). **Secrets do NOT go here** — they flow through the
backend credential/secret path (`acq secret …`), never the kit spec.
- `serviceGateways` — kit-declared, `acq`-managed service gateways. v1 uses
kit-local Compose files only (`runtime.compose.files[]`) and a required
Compose service selector (`runtime.compose.service`), then exposes the
resolved gateway URL to the sandbox/agent via `expose.env` (for example,
`WEB_GATEWAY_URL: url`). Existing `files[]` and `commands[]` remain responsible
for client-side software/config inside the sandbox. The goal is not broader
sandbox egress or API keys in the agent; it is a narrow, policy-controlled
gateway endpoint. Local kit sources are allowed for development/private kits;
remote service-gateway kits must come from trusted kit sources, but v1 does not
add a machine-readable trusted-source gate to the schema or validator. The
schema intentionally excludes host/guest IPs, DNS, VSOCK, Podman-machine,
Kubernetes, and backend-specific routing details.
- `backend_shortcuts.<backend>` — a native primitive that replaces the
declarative path for one backend (e.g. msb's `--trust-host-cas` for the
Zscaler kit). Adapters check this first; if present, `caps`/`files`/`commands`
Expand Down
Loading