-
Notifications
You must be signed in to change notification settings - Fork 144
PostgreSQL community pinboard #435
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@dagwieers , thank you for this invatation! If nobody is reasonably against I'd like to actively lead this group. I hope everything works out. |
@Andersson007 Great and thanks ! We do allow more than one leading a Working Group, as long as it helps moving forward and engages the community as a whole I support every new idea. There are no strict rules we try to learn as we go with this new concept of technology-related communities. There's a lot of open PRs to review and open issues to verify, so everyone is welcome to make the upcoming Ansible v2.8 release the best one for PostgreSQL support. We have about one more month to get our act together! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Who can explain me a couple of questions about writing and execution of integration tests? |
@Andersson007 Integration tests live in our tree in test/integration/targets/. I wrote some information about integration tests at: https://github.com/ansible/community/wiki/Reviewing#integration-tests My integration tests typically look like this: https://github.com/ansible/ansible/blob/devel/test/integration/targets/mso_tenant/tasks/main.yml Running an integration test is done using: $ ansible-test integration --allow-unsupported <target-name> You can add |
@dagwieers, thank you for this useful info! I hope it will be useful for all. This is convenient to use docker for this. I tried to run - nothing difficult. |
Thanks Andrey for working on this. I also started fiddling with docker today. I did a 11.5 miles run today and my energy was spent there.
I noticed all the useful comments you wrote on ansible/ansible#50568 <ansible/ansible#50568> and I hope to get started implementing this slowly.
My current work does not use postgresql so I need to get to run postgresql in docker first to do some exploratory research such as finding which query gives
the options of a tablespace in case one is working on an existing tablespace and the code needs to check whether the current options match the options requested by the user.
Regards,
Antoine
… On Feb 2, 2019, at 2:14 PM, Andrey Klychkov ***@***.***> wrote:
@dagwieers <https://github.com/dagwieers>, thank you for this useful info! I hope it will be useful for all. This is convenient to use docker for this. I tried to run - nothing difficult.
I'm going to try to write tests for all of my new recent modules
and, if success, maybe for existing modules without tests.
Would be better if other contributors from working group help to add this tests for them too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#435 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAckbGC5JoiIsv85Ofjttn8ELlIB6VRaks5vJeN7gaJpZM4acdcw>.
|
This comment has been minimized.
This comment has been minimized.
Great idea. I've been wondering if a collective push towards a better structure of the PostgreSQL integration would not be sensible. |
This comment has been minimized.
This comment has been minimized.
@frittentheke Proposals and ideas are welcome. One of the first actions of the GitLab WG was to refactor all GitLab modules. IMO it is best we first implement integration tests for the existing code before we refactor these modules. |
Three modules expect reviews (The last week I added session_role and CI tests for them, improved documentation): |
ansible/ansible#51477 needs to be tried manually. Can anybody run it locally and do shipit if success? (it needs installed psycopg2 as usual) |
This comment has been minimized.
This comment has been minimized.
@alikins Hello, I remember you've suggested some help with it but I can't recall where ;) Could you send me a test message to aaklychkov at mail dot ru ? I'd like to ask you a couple of questions about general things. |
And if anyone needs review or help for his/her postgresql related PRs, please, let me know (you can do it directly by my email written in the message above). |
Hey, guys. This is the new module PR ansible/ansible#39902. |
@Andersson007 : I can have a look at |
@sebasmannem , cool, I think if @jbscalia won't answer us before the end of this week, it would be great if you rewrite it ) Thanks! |
@sebasmannem , also, would be great, if you look at several new modules that are waiting for review. |
FYI: I've just started a new module called postgresql_vacuum |
New module postgresql_vacuum is ready for review |
@AsgerPetersen hey! we have the community pinboard here to communicate and WG where you can find some ideas to implement, add your own, and find things that need reviewing/opinions. You can write yourself into a members table there by editing the wiki page and subscribe here if you like :) |
who is interested in not to go to servers when vacuum is needed, please, look at postgresql_vacuum ;) |
Hello all! My opinion: the point is doing vacuum/analyze/vacuum full remotely by ansible specific module
at least the example above looks more elegant and in ansible style than:
For example, 1. I uploaded the data by postgresql_copy module to a table then 2. I'd like to use a specific module for analyze, not shell like above (Moreover, users don't need to know SQL at all to do it) |
Hello all! There are three news / suggestions
|
Ding Ding Ding, new module postgresql_publication is ready for review |
Hello all! The Feature Freeze is comming soon, ti will be in less than a week, so it is the last chance to see postgresql_publication merged ansible/ansible#59439 , could anybody please look at this |
Hey, dear colleagues! |
@Andersson007 yes sorry i miss too many time, thanks for your rewrite. Don't hesitate to write the subscription module to go with it for next release |
@nerzhul hey, no problem! |
tomorrow i'm starting postgresql_subscription module. Hope it will be done at the end of next week (25.10.2019) |
postgresql_subscription is available for review ansible/ansible#63661 |
small reminder, ansible/ansible#63661 is ready for review |
hey, dear folks, and i congratulate you on 2.9 was released yesterday! |
for people who missed something, now all postgres stuff lives in community.general collection |
FYI: postgres related stuff has been copied to a separate collection called community.postgresql. |
all new issues/PRs need to be created in |
Hi all! |
FYI:
|
@gundalow feel free to close this issue |
@Andersson007 Thanks done. I've also changed the Ansible/community wiki to point to the new one. |
@gundalow thanks! |
This has all moved to community.postgres collection repository.
The text was updated successfully, but these errors were encountered: