Project

General

Profile

Actions

Bug #5937

closed

Enforce the content of the local ncf configuration file from techniques

Added by Nicolas CHARLES over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

In #5682, we introduced a new format for the ncf configuration file, by using a mustache template

We need to modify the way it is handled by the script rudder-upgrade which sed in it, regardless of the context
We need to obtain, at the end, a config file that owuld look like

{{#classes.any}}
# Which logger(s) should be used in ncf? (comma separated list)
loggers=_logger_default
{{/classes.any}}
# Which port should be for CFEngine connections/data transfers
{{#classes.community_edition}}
cfengine_port=5309
{{/classes.community_edition}}
{{#classes.enterprise_edition}}
cfengine_port=5308
{{/classes.enterprise_edition}}


Related issues 4 (0 open4 closed)

Related to Rudder - Bug #5682: Add a configuration file when using enterprise editionReleasedJonathan CLARKEActions
Related to Rudder - Bug #5980: have the path of the config file overridable ReleasedJonathan CLARKEActions
Related to Rudder - Bug #7452: New version of ncf_conf.cache may not be properly updated on nodes after an upgradeReleasedJonathan CLARKE2015-11-24Actions
Related to Rudder - Bug #7794: rudder-upgrade edits the wrong ncf.conf file causing transitory invalid promises during upgradesReleasedVincent MEMBRÉ2016-01-19Actions
Actions

Also available in: Atom PDF