kevinveenbirkenbachandClaude Opus 5.5 77cab6e40b perf(svc-swarm-node): read the ingress ports and the node addresses in one shell ...

The ingress guard read ran two remote shells per swarm deploy, each asking container info again (WordPress#0 run 41303726270: 66 s + 61 s over 64 calls each). One shell now prints 'port <json>' and 'node <address>' lines into swarm_ingress_read; the new swarm_ingress_sections filter splits them by tag and raises on any untagged line, and SWARM_INGRESS_GUARDED and SWARM_INGRESS_PEERS read their section, so the guarded set, the peers, the firewall digest and the ruleset stay the same. A test ties the --format tags in read.yml to the sections the filter knows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-03 16:38:05 +01:00

..

action

perf(stack_host_copy): settle an unchanged directory copy in one remote call

2026-11-01 16:35:01 +01:00

filter

perf(svc-swarm-node): read the ingress ports and the node addresses in one shell

2026-11-03 16:38:05 +01:00

lookup

feat(constructor): stop a deploy in a pre-flight when the host cannot carry it

2026-11-03 13:38:15 +01:00

__init__.py

…