Actions
Bug #5574
closedUser story #5571: Permit the nodes access rules to be reloaded automatically after each promises generation (was Promises are reloaded by cf-serverd only every 5 minutes)
Have a configuration property to execute a post promise writing hook
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Once the promises have been written, we may need to execute a command (like, SIGHUP'ing cf-serverd to force it to reload its promises
Updated by Nicolas CHARLES over 9 years ago
Option is rudder.cfengine.reload.server.command
so that we know it is really for that, and nothing else
Updated by Nicolas CHARLES over 9 years ago
- Status changed from In progress to 10
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder/pull/617
Updated by Nicolas CHARLES over 9 years ago
- Status changed from 10 to Pending release
- % Done changed from 0 to 100
Applied in changeset 08d8ce239a5153a5bd38ec612af5f46516980dfe.
Updated by Nicolas CHARLES over 9 years ago
Applied in changeset f086ee48638f9ef29a7cb813de4a2c7adc286461.
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.4, which was released today.
- Announcement
- Changelog
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Jonathan CLARKE over 9 years ago
- Subject changed from Have a configuration property to execute a post promise wrinting hook to Have a configuration property to execute a post promise writing hook
Updated by Benoît PECCATTE about 9 years ago
- Category changed from 14 to Web - Config management
Updated by Benoît PECCATTE almost 9 years ago
- Tracker changed from Enhancement to Bug
Actions