Anso b611f41872 fix(drift): stop flagging declared external networks as drift (#1402) ...

The spatial drift engine reported a service attached to a declared
external network (top-level networks: { foo: { external: true } }) as
"attached to a network not declared in compose", marking the stack
permanently drifted. runtimeResourceName project-prefixed every declared
network to <project>_<key>, but Docker never prefixes an external
network: it references a pre-existing network by its real name. The
phantom <project>_<key> never matched the runtime name, so the
attachment fell through to a foreign-network finding.

Resolve external networks to their real name (the key, or a name:
override) without the project prefix, so the raw declared adapter agrees
with the rendered model the Network Inspector already used. Add unit,
adapter, and engine-level regression tests, and extend the adapter
equivalence test to cover an external network with no name override.

2026-06-21 17:58:00 -04:00

..

composeNetworkInspector.ts

feat(stacks): per-stack environment inventory and secret-safe guardrails (#1397)

2026-06-20 11:58:42 -04:00

networkingSummary.ts

feat: Compose Network Inspector and exposure intent guard (#1360)

2026-06-12 02:15:11 -04:00

normalize.ts

fix(drift): stop flagging declared external networks as drift (#1402)

2026-06-21 17:58:00 -04:00

types.ts

feat: Compose Network Inspector and exposure intent guard (#1360)

2026-06-12 02:15:11 -04:00