Postgres support

[alek-github]

Description

Added postgres support to kafkaflow-retry-extensions based on the implementation for sql server. It's needed to enable using the package with postgres db. Decided to make it as similar as possible to sql code, to make sure it's aligned to the existing style & practices and does not cause any discrepancies. Further adjustments of extracting shared code could be done in separate PRs, after confirming it with the repo owners. All of the postgres adjustments (comparing to sql code/scripts) can be viewed by skipping first commit

How Has This Been Tested?

Run all unit tests and integration tests locally to make sure that new integration works. New integration is covered same way as sql server

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have added tests to cover my changes
• I have made corresponding changes to the documentation

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

[alek-github]

Would appreciate Your review @luispfgarces @filipeesch @fernando-a-marins

[luispfgarces]

Implementation seems to be very alike the SQL Server implementation. Many of the things are duplicated, but I agree that this could not be accomplished without doing it (at least without a structural refactor).

I am leaving just 2 comments on minor things to solve, nothing that poses a big deal. Thank you @alek-talabat for your contribution. On my end, I'll approve once you fix those 👌

[luispfgarces]

We need to merge #93 to fix the build pipeline (support for builds with forked repositories).

[luispfgarces]

Thank you for your changes @alek-talabat. LGTM

[luispfgarces]

@alek-talabat the PR #93 was merged, which will fix your build pipeline. Please merge from main branch.

[martinhonovais]

Hi @alek-talabat,
First of all, many thanks for your contribution, we are very glad to review it.
Everything seemed good to me but I have some considerations:

1. I feel that we could have a sample using the PostgresSql repo. This could help the PostgresSql users experimenting the repo with not too much effort.
2. Last week we merged to main a feat that allows the dev to apply a retention policy for queues that have been done. Please take it into consideration in your PR as well. It will help devs to save repo space and money.
3. Let us know if you did some API's tests using PostgreSql as a repo and if it went well.

[gsferreira]

• I feel that we could have a sample using the PostgresSql repo. This could help the PostgresSql users experimenting the repo with not too much effort.

@alek-talabat the sample can be a different PR.

And by the way, excellent contribution right here! 👏

[luispfgarces]

@alek-talabat can you please check the build error?

Error: /home/runner/work/kafkaflow-retry-extensions/kafkaflow-retry-extensions/src/KafkaFlow.Retry.Postgres/RetryQueueDataProvider.cs(18,52): error CS0535: 'RetryQueueDataProvider' does not implement interface member 'IRetryDurableQueueRepositoryProvider.DeleteQueuesAsync(DeleteQueuesInput)' [/home/runner/work/kafkaflow-retry-extensions/kafkaflow-retry-extensions/src/KafkaFlow.Retry.Postgres/KafkaFlow.Retry.Postgres.csproj]

I think that the pull request that went Live before yours created a new method on the repository interface, which yours does not have (because you implemented it before this change).

Thank you! 🙏

[alek-github]

Sorry for the delay, but changes from the most recent master are already included. Would appreciate Your reviews @martinhonovais @gsferreira to have this one closed