As described in https://node-postgres.com/features/ssl , `ssl` is an object which will be passed to Node TLS socket.
Also:
```
(node:1) DeprecationWarning: Implicit disabling of certificate verification is deprecated and will be removed in pg 8. Specify `rejectUnauthorized: true` to require a valid CA or `rejectUnauthorized: false` to explicitly opt out of MITM protection.
```
This change makes it possible to configure accepted SSL CA certificate, or to accept self-signed certificate.
Defining "enableLegacyRoutes" as "true" is less secure than setting it to "false" by default, according to the documentation in "Securing Unleash" (https://unleash.github.io/docs/securing_unleash).
* feat: move secrets to settings
* feat: Add better support for detailed db options.
Added db field in options to allow better control of
db-options. Especially important to allow special chars
in database password which might lead to an invaid url
when defined as a database-url.
* fix: integrate logger with knex logger
* fix: remove secret option from all examples
* fix: more options.js unit tests
* fix: added settings-store e2e tests
* Support construct database by multiple env variable
* fix typo for test
* Add small change for passord and support ssl
* consider ssl should be true always
Instead of instructing users to do static calls
in to Unleash, she should instead be allwed to
specify the log provider as an option to Unleash.
This commit introduces the "getLogger" option,
a function responsible for creating a logger.
Because all request details are available via
prometheus there is no need to also log all requests.
This solves #164 but we should still replace log4j with something else.
