Meltano supported tap-postgres

[pnadolny13]

• Repo: https://github.com/MeltanoLabs/tap-postgres
• Slack channel: https://meltano.slack.com/archives/C04CLA0S4G0/p1669058552528759

Development Scope:

• [x] tagged release
• [x] tests pass in CI
• [x] branch protection
• [ ] cookiecutter TODOs completed and removed
• [ ] clean README
• [x] Added to meltano hub
• [ ] feature coverage relative to Hub default https://hub.meltano.com/extractors/tap-postgres--transferwise/ ?
  • [ ] https://github.com/MeltanoLabs/tap-postgres/issues/30

Out of Scope Features Mentioned:

• https://github.com/MeltanoLabs/tap-postgres/issues/3
• https://github.com/meltano/sdk/issues/1343
• https://github.com/MeltanoLabs/tap-postgres/issues/31

[pnadolny13]

@tayloramurphy I created this to define the scope of development for these new plugins, track status, and decide when its ready to recommend. Can you help fill in the description with the features (specific to this source) we expect the initial release to support? It will help us and users understand what done is and when we're there.

cc @visch @aaronsteers

[visch]

This one needs some love that's for sure

These 4 are pretty straight forward and <a few hours of work.

1. tests pass in CI - https://github.com/MeltanoLabs/tap-postgres/pull/26 Quinn has this one pretty much done
2. branch protection - https://github.com/MeltanoLabs/tap-postgres/issues/27
3. cookiecutter TODOs completed and removed - https://github.com/MeltanoLabs/tap-postgres/issues/28
4. clean README- https://github.com/MeltanoLabs/tap-postgres/issues/29
5. CD together, with deploys to PyPi - https://github.com/MeltanoLabs/tap-postgres/issues/31

Feature coverage missing things. I can't say what should/shouldn't be there before we make the default switch but here's generally the "Important" missing features. The biggest thing transferwise has over this tap is that they have had their tap around longer so it's just seen more stuff in the wild

1. Log based pulls - https://github.com/MeltanoLabs/tap-postgres/issues/3
2. SSL / Username / Host broken out configurations - https://github.com/MeltanoLabs/tap-postgres/issues/30

[aaronsteers]

@visch - Thanks for logging these. We have an emerging standard practice for CD deployments to PyPi, so I think it's safe to leave that out or do manually a few times for now.

I do agree this one is important since it may front-load some breaking changes:

• https://github.com/MeltanoLabs/tap-postgres/issues/30

This can come along a little later when higher priorities are all addressed:

• https://github.com/MeltanoLabs/tap-postgres/issues/3

Agreed SSL is a nice-to-have and important but perhaps not yet "urgent". After we build into tap-postgres (and/or target-postgres), the long-term plan is to work this into the SDK as well:

• https://github.com/meltano/sdk/issues/1343

[pnadolny13]

@aaronsteers @visch this is great! I updated the issue checklist with what I think is the consensus in/out of scope items. Definitely feel free to change them if more stuff comes up thats blocking us recommending this variant.