Bug #5324: ncf should write techniques using ifvarclass instead of direct classes - Rudder - Issue Tracker

Actions

Copy link

Bug #5324

closed

ncf should write techniques using ifvarclass instead of direct classes

Added by Vincent MEMBRÉ over 10 years ago. Updated over 2 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Nicolas CHARLES

Category:

Generic methods

Target version:

ncf-0.x

Pull Request:

https://github.com/Normation/ncf/pull/92

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

We are currently writing technique with ncf using the folowing syntax:

class::
  "method_call" => method(args...);

this does not work when class are based on variable ...and we should use the ifvarclass syntax

"method_call" => method(args...),
  ifvarclass => "class";

Actions

Copy link

Updated by Nicolas CHARLES over 10 years ago

On 29 juillet 2014 17:52:50 CEST, redmine@rudder-project.org wrote:

Issue #5324 has been reported by Vincent MEMBRÉ.

----------------------------------------
Bug #5324: ncf should write techniques using ifvarclass instead of
direct classes
http://www.rudder-project.org/redmine/issues/5324

Author: Vincent MEMBRÉ
Status: New
Priority: 1
Assignee: Vincent MEMBRÉ
Category:
Target version:
Pull Request:

We are currently writing technique with ncf using the folowing syntax:
>class::
>  "method_call" => method(args...);
>
this does not work when class are based on variable ...and we should
use the ifvarclass syntax
>"method_call" => method(args...),
>  ifvarclass => "class";
>