Project

General

Profile

Actions
Copy link

Bug #17846

closed

Directive parameters are not passed to DSC Agent command_execution when it contains an underscore _

Added by Bas B over 4 years ago. Updated 10 months ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Config management
Target version:
old 6.1 issues to relocate
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

If a DSC Technique uses a parameter with an underscore, then the input which is set in the Directive is not passed to the DSC Agent. Parameters which doesn't contain an underscore are working fine (DSC Agent version: Rudder (Windows DSC) (6.1-1.19)).

Thanks, Bas

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #14371: At least on windows, technique editor parameters can not handle "_" charReleasedFélix DALLIDETActions
Actions
Copy link
 #1

Updated by Félix DALLIDET over 4 years ago

  • Related to Bug #14371: At least on windows, technique editor parameters can not handle "_" char added
Actions
Copy link
 #2

Updated by François ARMAND over 4 years ago

  • Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Priority changed from 0 to 70
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 4 years ago

We are rewriting on DSC parameters like "some_text" to "someText" - we are investigating why we are doing this, but this is probably because we've been overzealous in camelcasing.

Actions
Copy link
 #5

Updated by Nicolas CHARLES about 4 years ago

  • Category set to Web - Config management
  • Target version set to 6.0.9
  • Priority changed from 70 to 68

related ticket https://issues.rudder.io/issues/18022 has been merged, but ticket don't show it. Fix should be avaialble in nightly plugin

Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.9 to 6.0.10
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.0.10 to 798
  • Priority changed from 68 to 66
Actions
Copy link
 #8

Updated by Benoît PECCATTE over 3 years ago

  • Target version changed from 798 to 6.1.14
  • Priority changed from 66 to 58
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
Copy link
 #17

Updated by François ARMAND 10 months ago

  • Status changed from New to Resolved
  • Priority changed from 58 to 0
  • Regression set to No

Resolved, as previous comment tells.

Actions
Copy link

Also available in: Atom PDF