Project

General

Profile

Actions

Bug #10379

closed

When upgrading to 4.1, rudder.community.checkpromises.command=/bin/true option is lost

Added by Nicolas CHARLES over 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Small
Priority:
14
Name check:
Fix check:
Regression:

Description

If we set rudder.community.checkpromises.command=/bin/true , it's to avoid check of generated policy
However, when we upgrade to 4.1, the post generation check is made by

/opt/rudder/etc/hooks.d/policy-generation-node-ready/10-cf-promise-check

so I ended up with much slower policy generation - and piling of validation that I did not expect

This is surprising


Subtasks 1 (0 open1 closed)

Bug #10418: checkpromise+sighup config should be commented in properties file and bad name of corresponding hookReleasedBenoît PECCATTEActions

Related issues 2 (0 open2 closed)

Related to Rudder - User story #10411: Add migration notes for 4.1RejectedAlexis MoussetActions
Related to Rudder - User story #10412: Add a convention for ".disabled" hooks to not be executedReleasedVincent MEMBRÉActions
Actions

Also available in: Atom PDF