didericis
ce744a85c4
tracker-policy-pr / check-pr (pull_request) Successful in 11s
test / integration-docker (pull_request) Successful in 17s
test / unit (pull_request) Successful in 49s
lint / lint (push) Failing after 2m49s
test / integration-firecracker (pull_request) Successful in 3m35s
test / coverage (pull_request) Successful in 18s
test / publish-infra (pull_request) Has been skipped
Group the gateway's data-plane modules into three service sub-packages mirroring the host-side trio (bot_bottle.egress / .supervisor / .git_gate): gateway/egress/ addon_core, addon, dlp_config, dlp_detectors gateway/supervisor/ server (was supervise_server) gateway/git_gate/ render, http_backend Prefix-stripped filenames now that the package namespaces them; each sub-package has a thin docstring __init__ (no eager imports, cheap leaf loads). The two cross-cutting files stay at the gateway root: policy_resolver (shared per-client lookup) and gateway_init, renamed to bootstrap now that gateway/ already namespaces it. Updated all importers (bot_bottle + tests), the in-VM/container `-m` launch strings, the Dockerfile.gateway addon shim + ENTRYPOINT, and the five gateway entries in scripts/critical-modules.txt. Full unit suite green (2243). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
10 lines
513 B
Python
10 lines
513 B
Python
"""Gateway-side (data-plane) egress service: the mitmproxy addon and its
|
|
pure decision core, DLP detectors, and route/DLP config parsing.
|
|
|
|
These are the long-running data-plane pieces (loaded by mitmdump inside the
|
|
`bot-bottle-gateway` image), distinct from the host-side `bot_bottle.egress`
|
|
service that renders routes and prepares env. Import the concrete modules
|
|
directly (`from bot_bottle.gateway.egress.addon_core import ...`) — this
|
|
package deliberately does no eager work so leaf imports stay cheap.
|
|
"""
|