Mongodb tap does not support SSL (when forced on mongodb server side)

[gerardjp]

Is your feature request related to a problem? Please describe.
I've set up a tap/target from mongodb to Postgres, but I can't configure the use of SSL when using a mongodb tap. On the remote mongodb server we force the use of SSL, but without forcing client side SSL indentity validation. So it's loosely implemented, but minimally, (it should be) at least encrypted.

Since SSL is mandatory by GDPR legislation, to name one, and it's not uncommon for people to replicate data between remote sites. One would think this is a minimum requirement nowadays.

Describe the solution you'd like
Add the relevant parm(s) to pipelinewise tap config that singer.io already supports. See the SSL boolean already in the Singer tap config: https://github.com/singer-io/tap-mongodb

Describe alternatives you've considered
A workaround is setting up a site-to-site vpn so encryption takes place on a different layer (OSI network layer instead of application layer). However, this is overkill if one replicates several database from multiple different geographical locations into a single datawarehouse.

Additional context
I had a similar issue with replicating a Postgres instance from GCP (Google cloud platform) a while back, where there were configuration limitations on Postgres on the GCP side and could not make it work. There we also implemented a site-to-site vpn, but it's cumbersome and overkill. In this case we needed to replicate multiple instances so the vpn server setup was less overhead. However, since the different database engines like Postgres and Mongodb and possibly others support SSL/TLS one would expect the client side to support SSL on this.

Thanks a lot!