Using external DB other than Postgres does not work about charts HOT 7 CLOSED

@mellena1 - I think this is now fixed with #115. We move the pulling of the driver to a artifactory.preStartCommand now.
See the updated README.

from charts.

i have tried it and it is not fixed.
there are 2 different issues.

1. if i still want to use postgres but external - db.properties is not updated and still tries to go for the pod with postgressql
2. when switching to mysql i get the following:
   ERROR: /var/opt/jfrog/artifactory/etc/db.properties already exists and is set to a DB different than mysql
   no matter if i change it in the values file or via command like with --set i get the same results.

from charts.

@vital4ik - the db.properties is created on initial install and is persisted without being updated between upgrades (intentional behaviour). If you want to update it, you have to manually change it.
Was your attempt on a clean install or upgrade?
Also, please share the config you tried.

from charts.

@eldada thank you for your reply, i found out that when i do helm delete --purge it does not delete the PVC volumes. when i manually deleted and reinstalled using the template it worked.
one thing to mention, if possible add SSL value into the values file for mysql 5.7 and above and into the template.I had to specify the URL in order to work over it instead of host/port values.

from charts.

Thx for the update @vital4ik. Adding support for SSL to DB config is planned to be added in the future.

from charts.

@eldada do you know when the SSL option will be added to the DB config? this is a blocker currently.

from charts.

Sorry - I don't have an ETA yet.

from charts.