Skip to content
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-1761) Provide defined resource for managing recovery.conf #603

Merged

Conversation

dacrome
Copy link
Contributor

@dacrome dacrome commented Mar 30, 2015

Currently there is no resource to use for creating the recovery.conf

This resource can create a recovery.conf for replication with all
currently supported parameters

Currently there is no resource to use for creating the recovery.conf

This resource can create a recovery.conf for replication with all
currently supported parameters
jonnytdevops added a commit that referenced this pull request Mar 31, 2015
(MODULES-1761) Provide defined resource for managing recovery.conf
@jonnytdevops jonnytdevops merged commit 40061ba into puppetlabs:master Mar 31, 2015
@jonnytdevops
Copy link
Contributor

Thanks for your contribution! It looks great!

@dacrome
Copy link
Contributor Author

dacrome commented Apr 9, 2015

Nice! When will it be released?

@Envek
Copy link
Contributor

Envek commented Jan 12, 2017

Hi, guys!

I've found an issue in this PR: if I set manage_recovery_conf to true in postgresql::server and will not provide postgresql::server::recovery at all, empty recovery.conf file will be created and PostgreSQL will refuse to start.

Does anyone have any ideas how to fix or avoid this? It seems that problem is how puppetlabs-concat module works. Is there possibility to make it to remove file if there is no fragments exists?

More info: https://tickets.puppetlabs.com/browse/MODULES-4276

cegeka-jenkins pushed a commit to cegeka/puppet-postgresql that referenced this pull request Oct 23, 2017
…covery_conf

(MODULES-1761) Provide defined resource for managing recovery.conf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants