User story #10412
closedAdd a convention for ".disabled" hooks to not be executed
Description
In #8353, we added hooks. It was decided at the time that we will choose which scripts to execute based on the exec bit of the file. It means that to disable a script, you "set -x" it.
Now, there is a commonly used convention that in that kind of context, a ".disabled" script will not be executed even if it is set +x.
To be more general, it should be a list of excluded extension, which could also takes care of "rpmnew" and other things.
The documentation will need to be updated accordingly.
The list of suffixes that will make a hook be ignored is defined in /opt/rudder/etc/rudder-web.properties => rudder.hooks.ignore-suffixes
Updated by François ARMAND almost 8 years ago
- Related to Bug #10379: When upgrading to 4.1, rudder.community.checkpromises.command=/bin/true option is lost added
Updated by François ARMAND almost 8 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND almost 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1592
Updated by François ARMAND almost 8 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|1b3ff90e2d41d3e021e9739626e40adad10226a9.
Updated by Benoît PECCATTE over 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.0 which was released today.
- 4.1.0: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/