Project

General

Profile

Actions

User story #5673

closed

Add support to parameters in ncf techniques written with ncf builder

Added by Benoît PECCATTE over 8 years ago. Updated 8 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Technique editor
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Regression:

Description

We want to add the ability for a user to add parameters to a technique when writing it with ncf builder.

These parameters can be used as arguments to ncf methods calls.
These parameters must be exported to redderified techniques to make them available within directive forms.


Subtasks 11 (0 open11 closed)

User story #5665: Generate technique with parameter from ncfReleasedVincent MEMBRÉ2014-10-21Actions
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
User story #5674: Add technique parameter support to ncf api RejectedVincent MEMBRÉActions
User story #5675: Generate a caller bundle when creating a rudderified techniqueRejectedActions
User story #5679: Add technique variables support to ncf api RejectedActions
User story #5680: Manage technique parameters when rudderifying an ncf techniqueRejectedActions
Bug #11992: Techniques created in the technique editor don't show up in Rudder directive treeReleasedFrançois ARMANDActions
Bug #12072: rudder_reporting needs to have parameters if technique has parameters tooReleasedBenoît PECCATTEActions
Actions #1

Updated by Benoît PECCATTE over 8 years ago

We want to add the ability for a user to add parameters to a technique when writing it with ncf builder.

These parameters can be used as arguments to ncf methods calls.
These parameters must be exported to redderified techniques to make them available within directive forms.

Actions #2

Updated by Benoît PECCATTE over 8 years ago

  • Description updated (diff)
Actions #3

Updated by Alexis Mousset over 6 years ago

  • Category set to Technique editor - API
Actions #4

Updated by Alexis Mousset almost 6 years ago

  • Target version changed from 0.x to master
Actions #5

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from master to 4.2.2
Actions #6

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.2.2 to 4.2.3
Actions #7

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.2.3 to 4.2.4
Actions #8

Updated by Vincent MEMBRÉ about 5 years ago

  • Related to deleted (User story #5665: Generate technique with parameter from ncf)
Actions #9

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.2.4 to 4.3.0~beta1
Actions #10

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions #11

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/ncf/pull/669
Actions #12

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:8e9bd0f86d6054d2c67283fee2c8108065d8b33d.

Actions #13

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.0~beta1 which was released today.

Actions #14

Updated by Alexis Mousset 8 months ago

  • Project changed from 41 to Rudder
  • Category changed from Technique editor - API to Web - Technique editor
Actions

Also available in: Atom PDF