-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
SFTP Destination #4875
Comments
Hello! Would like to know if there's any update on this? I'm also looking to use SFTP as a destination. @mystmaker33 did you find some solution for this? |
Hey @snikhil24, @mystmaker33 |
Hey! I'm cleaning up issues, and want to clarify. So we have |
Personally I think a configurable destination format makes the most sense,
as different vendors need their files formatted differently.
…On Sun, Oct 13, 2024, 8:11 PM Natik Gadzhi ***@***.***> wrote:
Hey! I'm cleaning up issues, and want to clarify. So we have
destination-sftp-json, and you'd like to have destination-sftp-csv, is
that it? Would it be a better fit to have destination-sftp with
configurable format instead?
—
Reply to this email directly, view it on GitHub
<#4875 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEHJLVMVOTBYOCODZ7YGLP3Z3MD4LAVCNFSM6AAAAABP35JTN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZGQZTIMRTGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Any updates on an SFTP destination for CSV? |
Tell us about the new connector you’d like to have
I would like an SFTP destination for csvs based on tables in my database.
Describe the context around this new connector
We often need to regularly output csv files for our vendors with our data in them. Many of them use SFTPs to receive the csvs.
Describe the alternative you are considering or using
Right now I have scheduled python scripts that query our database, write the csv and post it to the desired SFTP
Are you willing to submit a PR?
Maybe! I can take a look, but don't want to guarantee anything :)
The text was updated successfully, but these errors were encountered: