Fixes: #234 - customInit: Can't find config setting

[mgruner]

Which issue this PR fixes

• fixes customInit: Can't find config setting  #234

Special notes for your reviewer

• The solution was basically to first execute postgresql-init, and only then zammad-init, which also needed the database envs to be able to run Rails commands.
• toYaml seemed to break multiline statements, so I removed it - not entirely sure

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• Chart Version bumped

[monotek]

i wonder why zammad-init is not the last one anyway?
maybe elasticsearch init should be moved above too?

[mgruner]

i wonder why zammad-init is not the last one anyway? maybe elasticsearch init should be moved above too?

I believe the order makes sense now:

• postgresql-init handles database installation and migration.
• zammad-init handles application (pre)configuration. This might also affect the next step:
• elasticsearch-init rebuilds the ES index.

From my pov this should work and is also kindof similar to how zammad-init works in zammad-docker-compose. Of course we can add a customInit also to elasticsearch-init later if it turns out to be required. Ok?

[monotek]

Or we're making it an own init step?
If zammad / custom init is importand for elasticsearch init might it there be a case where it's importand for postgres init too?

[mgruner]

For me the present proposal seems to be sufficient at this time. Of course, by mounting custom configMaps, everything can be overridden for special scenarios.

[mgruner]

We cannot run it before postgresql-init because this handles the seeding of the database, which is required to store Settings.