User story #8353
Updated by Janos Mattyasovszky over 7 years ago
It would be good to have the ability to implement server-side hook on different events on the rudder server(s). Example: - Auto-Accept/Deny nodes if they meet a specific criteria - Create a node-specific file and extend the private-folder of a node (#8352) This could be enabled by having a hooks.d directory, which executes all binary files inside the hook_name (when it exists): <pre> /opt/rudder/hooks.d/: -> policy-generation-started/ -> policy-generation-finished/ -> node-policy-generated/ -> node-non-compliant/ -> inventory-first-received/ inventory-received/ -> inventory-updated/ </pre> This would allow to introduce new hook, and add a easy way for the sysadmins to set up additional actions when things happen. You could add information in env.vars (RUDDER_*) to the binary being run, so one would know like *RUDDER_NODE_UUID*.