Tomas

Hi, I haven't looked at this issue yet. I just don't have the tike at the moment and other contributors are working on other things. On 2020-12-15, Tue at 18:43,...

I think we already covered this in discussion on #58 - you can specify a masterRole that already owns the database and schemas and postgres-operator will not create a new...

Not at all, I've used ginkgo in my past projects and it's fine. Thanks for hetring started with the tests!

For operator controller(s) logic, we could use mocked PG package, which we could generate. As for the actual Postgres package, we'd have to use integration tests, running tests in docker-compose...

Yes, agree on the unit tests to be first. I have written them for my other operator, it's pretty straight forward: https://github.com/movetokube/do-operator/tree/master/pkg/controller/dns As for integration tests, there's always an option...

I'm splitting this issue in two as it's quite big. One will be for unit and another for integration tests

All work for this issue to be tracked in #32 and #33.

Thanks for putting some work into this proposal. I was super busy since the January and will finally have some time to allocate to this project starting July

I'm planning to review this and other PRs and issues on Monday 08-29 as it's long overdue.

Hi @oxyno-zeta, > This one will allow to manage Postgres databases and users on multiple engines Do you mean Postgres on Azure and on AWS at the same time (with...