[EnMasse] Adapting the EnMasse deployment

[Lohmann Carsten (INST/ECS4)]

Hi,

we want to use EnMasse in connection with Eclipse Hono on Kubernetes. For that, we want to set a special config to be used by the dispatch router (i.e. qdrouterd.json).

However, with the current structure of the EnMasse deployment yml, this looks not so straightforward, as the nested JSONs in enmasse.yaml are not really readable
and that makes it hard to find the places where the structure can be adapted. It basically means changes have to be done in the jsonnet source files of the enmasse repo, re-creating the enmasse.yaml there.

It would look much easier to me, having an enmasse.yaml where there are top-level YAML structures instead of the nested JSON fragments. This would allow for changes directly in that file.
What were the motivations for using that nested structure and would it be feasible to change it to a non-nested structure that is easy to read and adapt?

TIA

Best regards

Carsten Lohmann

(INST/ECS4)
Bosch Software Innovations GmbH | Schöneberger Ufer 89-91 | 10785 Berlin | GERMANY | www.bosch-si.com<http://www.bosch-si.com>
Tel. +49 30 726112-130 | Fax +49 30 726112-100 | carsten.lohmann at bosch-si.com<mailto:carsten.lohmann at bosch-si.com>

Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/enmasse/attachments/20170614/a1f6f276/attachment.htm>