ssl and verify_mode fail when set as boolean values

[ilkkapeltola]

I have this tap installed separately and in meltano.
I need to use the config parameters 'ssl' and 'verify_mode'.
When running the tap alone, my config looks like this:

{ "user": "username", "password": "password", "host": "my-host.com", "port": 12345, "ssl": "true", "verify_mode": "false", "auth_database": "admin", "database": "settings" }

And this works, but only if ssl and verify_mode parameters are set as strings "true" and "false". Setting them as boolean true and false does not work.

This used to work with meltano too, but now for some reason this doesn't.
If I dump the config from meltano for this tap, it shows that in the config JSON, these two parameters are booleans, not strings.

{ "user": "username", "password": "password", "host": "my-host.com", "port": 12345, "ssl": true, "verify_mode": false, "auth_database": "admin", "database": "settings" }

and thus, the connection times out.

[ilkkapeltola]

Perhaps this is not an issue exactly, but something that could be improved so that both string and boolean values could work.
It's a bit confusing that they need to be strings.

[anden-akkio]

Also ran into this and it took me a while to figure out what was going on. Making them strings worked well.