Project

General

Profile

Actions

Bug #9402

closed

Node properties update doesn't invalidate node configuration hash

Added by François ARMAND about 8 years ago. Updated almost 8 years ago.

Status:
Released
Priority:
1 (highest)
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

If node properties are updated, and the properties are not used in a directive, then the node configuration hash is not updated. This is problematic because it means that the file .../properties.d/properties.json is not correctly synch with the real node properties.

Actions

Also available in: Atom PDF