Project

General

Profile

Actions
Copy link

User story #5665

closed

User story #5673: Add support to parameters in ncf techniques written with ncf builder

Generate technique with parameter from ncf

Added by François ARMAND about 10 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Web - Config management
Target version:
4.3.0~beta1
Pull Request:
https://github.com/Normation/rudder/p...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

We want to manage techniques from ncf, we have to do it for two things:

  • Generate metadata.xml and files for agent (dsc will be in another issue)
  • Modify generation to be able to generate correct bundle calls for our Directives

A small example of what we want
Let you have a technique "add_user" with 2 parameters:

bundle agent add_user(user_name, home_path)

This needs to create a technique with a Parameter Secion in metadata.xml with 2 simple inputs:

=> Two Input for variable USER_NAME and HOME_PATH

and a directive implementing this technique with parameters "toto" and "/home/toto".

We want to generate the following bundle call:

"Directive name" => add_user("toto","/home/toto")

Subtasks 4 (0 open — 4 closed)

Bug #5666: Directive form is laways empty when REPORTKEYS is presentRejected2014-10-21Actions
User story #5668: Include directive parameter in expected report substitution logicRejectedActions
Bug #5711: metadata.xml is considered malformed if it contains reportkeys and componentkeyRejected2014-10-29Actions
User story #5721: Add a REF element to REPORTKEYSRejectedFrançois ARMANDActions

Related issues 1 (0 open — 1 closed)

Blocked by Rudder - User story #5400: Use the existence of expected_reports.csv to detect if a technique is from ncfReleasedNicolas CHARLES2014-11-04Actions
Actions
Copy link

Also available in: Atom PDF