Project

General

Profile

Actions

User story #10412

closed

Add a convention for ".disabled" hooks to not be executed

Added by François ARMAND over 7 years ago. Updated over 7 years ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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


Subtasks 1 (0 open1 closed)

User story #10425: Add migration script for hooks ignore suffixesReleasedVincent MEMBRÉActions

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #10379: When upgrading to 4.1, rudder.community.checkpromises.command=/bin/true option is lost ReleasedAlexis MoussetActions
Actions

Also available in: Atom PDF