User story (meta) #2207
PT distributePolicy : Implement the SuSE postgresql configuration hack in the distributePolicy
| Status: | Released | Start date: | 2012-01-27 | |
|---|---|---|---|---|
| Priority: | 3 | Due date: | ||
| Assignee: |  Matthieu CERDA |
% Done: | 100% |
|
| Category: | Policy Templates | |||
| Target version: | Rudder - 2.4.0~alpha4 |
Description
PT distributePolicy : Implement the SuSE postgresql configuration hack in the distributePolicy
Related issues
Associated revisions
Fixes #2207: The distributePolicy now enforces the SuSE configuration hack for postgresql
Refs #2207: typo fix
Fixes #2207: The reports on distributePolicy now outputs some details when PostgreSQL has been restarted or failed to
History
#1
Updated by Matthieu CERDA over 1 year ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 3894a88df0a47b7ef7674d75910e3c1ccc9eeff1.
#2
Updated by Jonathan CLARKE over 1 year ago
- Status changed from Pending technical review to Discussion
This looks fine to me. Just one question: why not do any reporting on the outcome of the psql restart command promise? I think it's important to show an error if the restart command fails, because this could mean that we broke the config file somehow.
#3
Updated by Matthieu CERDA over 1 year ago
- Status changed from Discussion to In progress
- % Done changed from 100 to 80
Indeed. I'll fix it right away.
#4
Updated by Matthieu CERDA over 1 year ago
- Status changed from In progress to Pending technical review
- % Done changed from 80 to 100
Applied in changeset 47e42328db5c6d269bd06ed415fd91cc7d01277f.
#5
Updated by Jonathan CLARKE over 1 year ago
- Status changed from Pending technical review to Pending functional review
Looks good to me!
#6
Updated by Jonathan CLARKE over 1 year ago
- Status changed from Pending functional review to Released