Project

General

Profile

Actions

Architecture #7114

closed

Make the bundlesequence be defined in a dedicated bundle

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

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Effort required:
Name check:
Fix check:
Regression:

Description

Today, the bundlesequence is generated into promise.cf, what can be brittle and does not allow to add promisee for each bundle of the sequence.

We would like to genereate the bundlesequence in a dedicated file, with a list of "method / usebundle", and just call that bundle in promise.cf.


Subtasks 7 (0 open7 closed)

Architecture #7126: Add a new system variable for the "rudder_directives" bundleReleasedNicolas CHARLES2015-11-13Actions
Bug #7408: Empty inputs list is generated with double quotes even if emptyReleasedFrançois ARMAND2015-11-13Actions
Bug #7410: Fix variable use in #7408ReleasedFrançois ARMAND2015-11-13Actions
Bug #7412: Inputs lists are weirdly indented and don't follow our CFEngine conventions when generated by rudder-webReleasedFrançois ARMAND2015-11-13Actions
Bug #7413: Fix CFEngine conventions for generated files rudder_directives.cf and rudder_system_directives.cfReleasedNicolas CHARLES2015-11-13Actions
Bug #7454: Directives with double quotes in their name need to be escaped before going in rudder_directives.cf and rudder_expected_reports.csvReleasedVincent MEMBRÉ2015-11-24Actions
Bug #7363: Promises generation fails on 3.2ReleasedBenoît PECCATTE2015-11-03Actions
Actions

Also available in: Atom PDF