Meltano

Has something changed with the way config parameters are interpreted?
I had this working already, but now it's broken.

I'm using the transferwise variant of tap-mongodb and in it I need to use the parameters `ssl`=`"true"`  and `verify_mode`= `"false"`

For the tap to work, these do need to be strings, not booleans.

Now for some reason, meltano forces these to boolean values, which results in my pipeline to break. Where's the bug?

<@U06BXC4PAVD> thanks for calling this out! I added settings for that tap last week <https://github.com/meltano/hub/pull/727> because previously there were none. I used their readme as the basis for those settings but it looks like youre right based on <https://github.com/transferwise/pipelinewise-tap-mongodb/issues/75> and <https://github.com/transferwise/pipelinewise-tap-mongodb/blob/6dbc3ec64a36209e1c317fe49ed2ff7eea515d43/tap_mongodb/__init__.py#L260> theyre expecting a lowercase string `true` instead of a boolean value.

I can update the hub to treat those as strings for now but if your issue is resolved in that repo would you mind opening an issue in meltanohub or creating a PR to get it switched back to a boolean? That would be incredibly helpful

I guess they'll reject my issue as "As Designed" :smile:
But if not, yeah I will come back to you.

Thanks! I created <https://github.com/meltano/hub/pull/751>

<@U06BXC4PAVD> that fix was merged! If you run `meltano lock tap-mongodb --update` it should pull the new definition lock file to your project