Add tools-gitlab lab scenario proving the tools-only install

Prove gitlab — the exemplar tools-only, outbound-only external-SaaS integration — installs: a scenario assigning gitlab to one node, and a test asserting the mesh-runtime-gitlab container comes up and stays up, logs [mesh-tools] serving 23 tool(s), binds its serve queues on the broker, and gets its own scoped account — all with NO valid GitLab token, the case the Servarr lesson is about. No gitlab arm is needed in build-module-runtime.sh: gitlab speaks HTTP and needs no extra CLI in the image. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
2026-09-06 01:33:52 +02:00
parent 62e479b9fe
commit c9619a17f4
2 changed files with 283 additions and 0 deletions
@@ -0,0 +1,42 @@
+# One machine that becomes a mesh and is then assigned gitlab — the exemplar of the tools-only,
+# outbound-only external-SaaS integration (novox/hq ADR 0039). gitlab is the thinnest converted
+# shape: NO service container, NO listener, NO provisioner — just a broker-bound runtime that serves
+# the module's GitLab tools under a scoped account. Its sibling in kind is unifi (a tooled app), but
+# gitlab has no server of its own to run alongside; it only ever calls out to a GitLab instance.
+#
+# The sharp point this bed proves is the Servarr lesson: the runtime MUST come up and serve its full
+# tool surface even with NO valid GitLab credentials — the lab has no real GitLab, and gitlab's own
+# token is a mesh-minted own-secret that points at nothing. gitlab's client is built lazily and never
+# throws at registration, so the runtime logs `[mesh-tools] serving 23 tool(s)` and binds its serve
+# queues regardless; a tool would only fail if it were actually invoked without real creds.
+#
+#   MESH_LAB_HOST_BINARY=.../mesh-host   MESH_LAB_BUNDLE=.../examples/substrate-first-node.lock
+#   scripts/build-module-runtime.sh gitlab builds mesh-runtime-gitlab:development into the local
+#   daemon, which this scenario stocks and serves by digest from its own registry. gitlab needs no
+#   service image — it is tools-only.
+scenario: tools-gitlab
+
+segments:
+  hosting:
+    kind: public
+    cidr: [192.0.2.0/24]
+
+machines:
+  anchor:
+    at: { segment: hosting, address: [192.0.2.10] }
+    inbound: allow
+    memory: 3GiB
+    cpus: 2
+
+images:
+  # The first-node substrate: store, broker, control.
+  - postgres:17-alpine
+  - cloudamqp/lavinmq:latest
+  - mesh-control:development
+  # gitlab's runtime, built by scripts/build-module-runtime.sh gitlab into the local daemon and
+  # stocked into the scenario's own registry, which is where the host pulls it from. There is no
+  # service image: gitlab is tools-only and outbound-only.
+  - mesh-runtime-gitlab:development
+
+place:
+  all: [host, runtime]