Project

General

Profile

Actions
Copy link

Bug #14386

closed

UI "settings" for management of hooks works inconsistently

Added by François ARMAND about 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
5.0.9
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
80
Name check:
Fix check:
Regression:

Description

Since https://issues.rudder.io/issues/14331, we can manage /opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check directly in the "Setting > General" UI. But if you disable it, reload the page, the hook seems to be enable again.

In fact, the permissions on /opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check are now "rw-r-xr-x". So the UI only changed the owner exec right, not group/other. We should change all exec rights of the hook.

Subtasks 1 (0 open — 1 closed)

Bug #14550: UI "settings" for management of hooks need Unix rightReleasedNicolas CHARLESActions

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #14331: Trigger agent update and run after policy server has finished policy generationReleasedAlexis MoussetActions
Actions
Copy link

Also available in: Atom PDF