From 7ede6272b7d3e578fd415e869614551ff2100f1c Mon Sep 17 00:00:00 2001
From: Stefan Bethke <stb@lassitu.de>
Date: Sat, 25 May 2024 11:03:17 +0200
Subject: [PATCH] Workaround for broken Zammad Scheduler database config

---
 .../templates/chaosknoten/configs/zammad/compose.yaml.j2      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/playbooks/templates/chaosknoten/configs/zammad/compose.yaml.j2 b/playbooks/templates/chaosknoten/configs/zammad/compose.yaml.j2
index 83efc2c..8d345de 100644
--- a/playbooks/templates/chaosknoten/configs/zammad/compose.yaml.j2
+++ b/playbooks/templates/chaosknoten/configs/zammad/compose.yaml.j2
@@ -1,6 +1,4 @@
 ---
-version: '3.8'
-
 {#
 https://github.com/zammad/zammad-docker-compose
 Docker Compose does not allow defining variables in the compose file (only in .env files), so we use Jinja variables instead
@@ -138,6 +136,8 @@ services:
   zammad-scheduler:
     <<: *zammad-service
     command: ["zammad-scheduler"]
+    volumes:
+      - /ansible_docker_compose/zammad-scheduler-database.yml:/opt/zammad/config/database.yml # workaround for connection pool issue
 
   zammad-websocket:
     <<: *zammad-service