Project

General

Profile

Actions
Copy link

Bug #11210

closed

NCF Variable expansion on node properties does not work

Added by Ferenc Ulrich over 6 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
5.0.19
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Hello,

I would like to run a command using NCF method command execution which has 2 arguments like so:

/usr/local/sbin/command.name.sh ${node.properties[SERVER][0]} ${node.properties[SERVER][1]}

node property SERVER is a json

["server0", "server1"]

the command executes successfully, although i get some error messages on the agent:

error: Broken variable expression, index brackets do not balance, in 'node#properties[SERVER][0_'
error: Broken variable expression, index brackets do not balance, in 'node#properties[SERVER][1_'

Please fix this bug in NCF.
Thanks,
Ferenc

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #11600: Result class containing {} are not properly canonizedReleasedBenoît PECCATTEActions
Actions
Copy link
 #1

Updated by Benoît PECCATTE over 6 years ago

  • Category set to Techniques
  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 52
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 6 years ago

Hello Ferenc!

Is it possible to send us the technique file generated ? or at least the extract of the command_execution method call in the technique file ?

The file is located in /var/rudder/configuration-repository/ncf/50_techniques/<bundle_name>/<bundle_name>.cf

Actions
Copy link
 #3

Updated by Nicolas CHARLES over 6 years ago

  • Related to Bug #11600: Result class containing {} are not properly canonized added
Actions
Copy link
 #4

Updated by Benoît PECCATTE over 6 years ago

  • Priority changed from 52 to 50
Actions
Copy link
 #5

Updated by Nicolas CHARLES almost 5 years ago

  • Target version set to 5.0.13
  • Priority changed from 50 to 0

Retargeting to 5.0
Ferenc, we were not able to reproduice, do you have a more concrete example ?

Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #9

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions
Copy link
 #12

Updated by Nicolas CHARLES over 3 years ago

  • Status changed from New to Rejected

I'm rejecting this one, we changed both agent and implementation on ncf, so i'm pretty confident it either succeed, or fail in a totally different way

Actions
Copy link

Also available in: Atom PDF