Open pranasziaukas opened 1 year ago
This is really a meltano question more than it is a tap question. From the tap perspective we need to focus just on the config file that's sent to the tap. My guess is the line feeds are mangled
Thanks for your response @visch.
I understand your perspective. I'll raise a pertinent issue in the Meltano repository. However, in my opinion, it's equally an implementation decision for the tap to manage SSH keys - which are inherently multi-line - as regular strings.
I wrote https://github.com/MeltanoLabs/tap-postgres/issues/100#issuecomment-1727697992. FWIW, I try to avoid storing raw SSH keys as environment variables precisely for the reason that newline characters are treated differently across systems and tools -- I tend to reference file paths (to SSH keys) or, if needs be, use base64 encoding to get rid of the problematic characters. Just my 2 cents.
Just getting started with Meltano, and testing this Postgres tap.
So far, I have the following (redacted)
meltano.yml
config:As well as the following
.env
fileI took the SSH key file content and replaced all new lines with
\n
, just like in the example test case https://github.com/MeltanoLabs/tap-postgres/blob/bcc0db15be8184f7d99126fdad7b3a20f7dd91e8/tests/test_ssh_tunnel.py#L14Furthermore, I checked out the tap code locally and ran my key against the helper method https://github.com/MeltanoLabs/tap-postgres/blob/bcc0db15be8184f7d99126fdad7b3a20f7dd91e8/tap_postgres/tap.py#L385
to be 100% sure that it's valid and detected as an RSA key type.
That's why I'm highly confused to see this when running
meltano config tap-postgres test
ValueError: Could not determine the key type
is certainly coming from theguess_key_type
method even though I have validated it as explained above. Is this a red herring? How to diagnose further?Thanks.