Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

singer target-redshift, not able to connect to Redshift due to issue with SSL #46

Open
phanib4u opened this issue Sep 19, 2020 · 1 comment

Comments

@phanib4u
Copy link

The connectivity was good to the redshift from dbeaver with a set of creds and was able to intract on the redshift. But the same creds and details when used with singer target-redshift, not able to connect.
The current target-redshift do not support passing "SSL true". Could you help with the same ?

@AlexanderMann
Copy link
Collaborator

We should be able to port over the enhancements made in Target Postgres for connection creation. There's also probably an enhancement to make here in general where we can allow for the full connection details to just be a dictionary we hand off to PsycoPG, but it would more closely match how we're creating/dealing with everything for S3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants