feat: add extra Docker networks to container config
All checks were successful
CI / cleanup-branch (push) Has been skipped
CI / build (push) Successful in 1m23s
CI / docker (push) Successful in 1m7s
CI / deploy-feature (push) Has been skipped
CI / deploy (push) Successful in 38s

Apps can now join additional Docker networks (e.g., monitoring,
prometheus) configured via containerConfig.extraNetworks. Flows through
the 3-layer config merge. Networks are created if absent and containers
are connected during deployment. UI adds a pill-list field on the
Resources tab (both create and edit views).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
hsiegeln
2026-04-12 16:53:01 +02:00
parent 5b6543b167
commit be96336974
4 changed files with 68 additions and 2 deletions

View File

@@ -147,6 +147,16 @@ public class DeploymentExecutor {
additionalNets.add(envNet);
}
// User-configured extra networks (e.g., monitoring)
if (networkManager != null && config.extraNetworks() != null) {
for (String net : config.extraNetworks()) {
if (!net.isBlank() && !additionalNets.contains(net)) {
networkManager.ensureNetwork(net);
additionalNets.add(net);
}
}
}
// === START REPLICAS ===
updateStage(deployment.id(), DeployStage.START_REPLICAS);
@@ -370,6 +380,7 @@ public class DeploymentExecutor {
map.put("deploymentStrategy", config.deploymentStrategy());
map.put("runtimeType", config.runtimeType());
map.put("customArgs", config.customArgs());
map.put("extraNetworks", config.extraNetworks());
return map;
}
}