MeltanoLabs / MeltanoLabs/tap-postgres
Support configuring SSH tunnel with a private key file
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Originally posted by @edgarrmondragon in https://github.com/MeltanoLabs/tap-postgres/pull/94#discussion_r1170478755
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the original discussion in pull request 94 and then locate the existing SSH tunnel configuration in the repository. Clarify the expected private-key-file configuration and verify that a tunnel can be established using it without breaking current PostgreSQL connection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100