-
Notifications
You must be signed in to change notification settings - Fork 614
Ensure multiple postgresql::server::recovery resources can be defined #1348
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
Ensure multiple postgresql::server::recovery resources can be defined #1348
Conversation
postgresql::server::recovery is a typethat may have no external impact to Forge modules. This module is declared in 70 of 579 indexed public
|
FYI I did accept the license agreement, system just doesn't seem to recognize it and the "recheck" link doesn't work. |
Can you try to rebase and force push? Perhaps that retriggers it properly. Other than that this change looks good. |
48c3ad0
to
6995d1d
Compare
@Deroin Look's like you have a few spec test failures:
Look's like some simple errors from the test's not being updated. |
44d40a6
to
6cc1aea
Compare
6cc1aea
to
0944a35
Compare
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
Sorry for the wait on the merge for this, had a bit of discussion on whether it changing the recovery files name counted as backwards incompatible or not.
In the end just decided on BugFix.
Anyway, thanks for putting in the work :)
As
postgresql::server::recovery
is a define it should support multiple instances of itself.With the
concat::fragment
having a fixed name this is not possible. Thus I just interpolated the name property into that so that one may create multiple recovery files in different locations, if required.