chore(theme): bump ZB.MOM.WW.Theme 0.3.0 -> 0.3.1 (interactive-render nav fix)

fix(docker-dev): persist dev SQL ConfigDb on a named volume
The docker-dev sql service had no volume, so its data lived in the container writable layer. A recreate silently dropped the OtOpcUa database and every host node failed its configdb health check (AdminUI 503) until an operator re-ran 'dotnet ef database update' + the cluster-seed. Add a named volume (otopcua-mssql-data -> /var/opt/mssql) so the migrated schema + seeded clusters survive 'docker compose up' cycles.
2026-06-05 07:19:11 -04:00 · 2026-06-05 05:26:34 -04:00 · 2026-06-05 05:07:02 -04:00
2 changed files with 12 additions and 1 deletions
@@ -108,6 +108,6 @@
    <PackageVersion Include="ZB.MOM.WW.Auth.Ldap" Version="0.1.1" />
    <PackageVersion Include="ZB.MOM.WW.Auth.AspNetCore" Version="0.1.1" />
    <PackageVersion Include="ZB.MOM.WW.Audit" Version="0.1.0" />
-    <PackageVersion Include="ZB.MOM.WW.Theme" Version="0.2.1" />
+    <PackageVersion Include="ZB.MOM.WW.Theme" Version="0.3.1" />
  </ItemGroup>
 </Project>
@@ -51,6 +51,13 @@ services:
      MSSQL_PID: Developer
    ports:
      - "14330:1433"
+    # Persist the ConfigDb across container recreates. Without this the dev SQL
+    # is ephemeral (container writable layer), so a recreate silently drops the
+    # OtOpcUa database and every host node fails its configdb health check until
+    # EF auto-migration + cluster-seed rebuild it. The named volume keeps the
+    # schema + seeded clusters between `docker compose up` cycles.
+    volumes:
+      - otopcua-mssql-data:/var/opt/mssql
    healthcheck:
      test: ["CMD-SHELL", "/opt/mssql-tools18/bin/sqlcmd -S localhost -U sa -P 'OtOpcUa!Dev123' -No -Q 'SELECT 1' || exit 1"]
      interval: 10s
@@ -307,3 +314,7 @@ services:
      - site-a-2
      - site-b-1
      - site-b-2
+
+volumes:
+  # SQL Server data dir — persists the OtOpcUa ConfigDb across container recreates.
+  otopcua-mssql-data:
Author	SHA1	Message	Date
Joseph Doherty	83b8d75112	chore(theme): bump ZB.MOM.WW.Theme 0.3.0 -> 0.3.1 (interactive-render nav fix) v2-ci / build (push) Failing after 46s Details v2-ci / unit-tests (tests/Core/ZB.MOM.WW.OtOpcUa.Cluster.Tests) (push) Has been skipped Details v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.ControlPlane.Tests) (push) Has been skipped Details v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.Tests) (push) Has been skipped Details v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Runtime.Tests) (push) Has been skipped Details v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Security.Tests) (push) Has been skipped Details v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.Host.IntegrationTests) (push) Has been skipped Details v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.IntegrationTests) (push) Has been skipped Details	2026-06-05 07:19:11 -04:00
Joseph Doherty	3e9793eff7	fix(docker-dev): persist dev SQL ConfigDb on a named volume The docker-dev sql service had no volume, so its data lived in the container writable layer. A recreate silently dropped the OtOpcUa database and every host node failed its configdb health check (AdminUI 503) until an operator re-ran 'dotnet ef database update' + the cluster-seed. Add a named volume (otopcua-mssql-data -> /var/opt/mssql) so the migrated schema + seeded clusters survive 'docker compose up' cycles.	2026-06-05 05:26:34 -04:00
Joseph Doherty	3e4450e0b1	chore(theme): consume ZB.MOM.WW.Theme 0.3.0 (nav/login kit fixes)	2026-06-05 05:07:02 -04:00