From dc6a8facee6065e5d50ac269e2d14a08c5cc9f31 Mon Sep 17 00:00:00 2001
From: Ralph Bean <rbean@redhat.com>
Date: Tue, 24 Oct 2017 11:37:58 +0000
Subject: [PATCH] Give the greenwave fedmsg consumer also access to the general
 greenwave config.

---
 .../greenwave/files/deploymentconfig.yml               | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/roles/openshift-apps/greenwave/files/deploymentconfig.yml b/roles/openshift-apps/greenwave/files/deploymentconfig.yml
index dbe2e547bf..3af774541c 100644
--- a/roles/openshift-apps/greenwave/files/deploymentconfig.yml
+++ b/roles/openshift-apps/greenwave/files/deploymentconfig.yml
@@ -82,6 +82,9 @@ spec:
         command:
         - '/usr/bin/fedmsg-hub'
         volumeMounts:
+        - name: config-volume
+          mountPath: /etc/greenwave
+          readOnly: true
         - name: fedmsg-config-volume
           mountPath: /etc/fedmsg-greenwave.d
           readOnly: true
@@ -95,10 +98,15 @@ spec:
           limits:
             memory: 384Mi
       volumes:
+      # Give the fedmsg-consumer container access to the general config
+      - name: config-volume
+        configMap:
+          name: greenwave-configmap
+      # But *also* access to the fedmsg-specific config
       - name: fedmsg-config-volume
         configMap:
           name: greenwave-fedmsg-configmap
-      # This secret volume gets set up in the playbook
+      # And... this secret volume gets set up in the playbook
       - name: fedmsg-key-volume
         secret:
           secretName: greenwave-fedmsg-key