New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(MODULES-11251) Add support for backup provider "pg_dump" #1319
Conversation
postgresql::backup::pg_dump is a classthat may have no external impact to Forge modules. postgresql::params is a classthat may have no external impact to Forge modules. postgresql::server is a classthat may have no external impact to Forge modules. This module is declared in 70 of 578 indexed public
|
Hi, |
Thanks for the review. Actually I've already had a look at puppet/dbbackup, but I really like the integrated approach of puppetlabs/mysql's backup feature, and I cannot use systemd, which lead to the creation of this PR. :) |
I've added some tests with the latest commit. |
This PR has been marked as stale because it has been open for a while and has had no recent activity. If this PR is still important to you please drop a comment below and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days. |
postgresql::backup::pg_dump is a classthat may have no external impact to Forge modules. postgresql::params is a classBreaking changes to this file WILL impact these 2 modules (exact match):Breaking changes to this file MAY impact these 3 modules (near match):postgresql::server is a classBreaking changes to this file WILL impact these 38 modules (exact match):
Breaking changes to this file MAY impact these 16 modules (near match):This module is declared in 70 of 579 indexed public
|
dear puppet, please do not autoclose PR that are only stale because nine of you reviewed it... @fraenki sadly this now needs a rebase, could you please do that? |
Hello! 👋 This pull request has been open for a while and has had no recent activity. We've labelled it with If you are waiting on a response from us we will try and address your comments on a future Community Day. Alternatively, if it is no longer relevant to you please close the PR with a comment. Please note that if a pull request receives no update for 7 after it has been labelled, it will be closed. We are always happy to re-open pull request if they have been closed in error. |
PR needs a review, I'll rebase ASAP... |
hey @fraenki ! Appreciated! |
@chelnak Rebased. Ready for review :) |
Hey @fraenki ! I'm on PTO this week so pinging @pmcmaw and @david22swan for assistance! |
@fraenki Look's like your getting a few spec test failures. |
I've force-pushed a fix, please re-run the spec tests. |
Since I'm unable to run the tests locally, I need to request a re-run of the spec tests again... :-/ |
The spec tests are finally passing. 🎉 |
@chelnak @david22swan What do you think? Can this PR be merged? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Apologies for the wait on this.
Anyway it look's good to me so I'm gonna go ahead and merge :)
Thank's for putting in the work
This adds support for backup "providers" to puppetlabs/postgresql. The feature is heavily inspired by a similar feature in puppetlabs/mysql.
See Puppet ticket for full details:
https://tickets.puppetlabs.com/browse/MODULES-11251