Project

General

Profile

Actions

Bug #14372

closed

Ncf techniques used in windows can not start with a numerical char

Added by Félix DALLIDET over 5 years ago. Updated about 1 month ago.

Status:
Released
Priority:
N/A
Category:
Web - Technique editor
Target version:
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:
Fix check:
Regression:
No

Description

Creating a ncf tehcnique starting with a numerical char like "0" will break the DSC agent, at least if the name contains a "-" in the name.
ex: "00-Kb-deployment"

Powershell will not understand and try to interpret the "00" part as a cmdlet and "-Kb" as a given cmdlet option.


Related issues 1 (0 open1 closed)

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

Updated by François ARMAND over 5 years ago

  • Target version changed from 5.0.7 to 5.0.9
Actions #2

Updated by François ARMAND over 5 years ago

  • Severity set 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 102

I set it to major as it can be extremelly hard for an user to understand what is happening given logs, and we advice to use that nomenclature in staring guide etc.

Actions #4

Updated by François ARMAND about 5 years ago

  • Assignee set to Vincent MEMBRÉ

That needs to be escaped on file system.

Actions #5

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.9 to 5.0.10
  • Priority changed from 102 to 101
Actions #6

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
  • Priority changed from 101 to 99
Actions #7

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions #8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
  • Priority changed from 99 to 97
Actions #9

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 97 to 94
Actions #10

Updated by François ARMAND over 4 years ago

  • Priority changed from 94 to 93

This is an hard limit of powershell, and besides doing some encoding on our side, we can't do
We will try to make some encoding for it => prefix generated method name ONLY ONE DSC AGENT with one character (like "r" or whatever).

Actions #11

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 93 to 92
Actions #12

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 92 to 89
Actions #13

Updated by Alexis Mousset over 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
  • Priority changed from 89 to 85
Actions #14

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #15

Updated by Nicolas CHARLES almost 4 years ago

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

Updated by François ARMAND almost 4 years ago

  • Target version changed from 5.0.18 to 6.0.8
Actions #17

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.0.8 to 6.0.9
Actions #18

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.9 to 6.0.10
Actions #19

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.0.10 to 798
Actions #20

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 798 to 6.1.14
Actions #21

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #22

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #23

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #24

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #25

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #26

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
  • Priority changed from 85 to 86
Actions #27

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
  • Priority changed from 86 to 88
Actions #29

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
  • Priority changed from 88 to 60
Actions #30

Updated by Alexis Mousset 7 months ago

  • Target version changed from old 6.1 issues to relocate to 7.3.10
  • Priority changed from 60 to 0
Actions #31

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.10 to 7.3.11
Actions #32

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 7.3.11 to 7.3.12
Actions #33

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 7.3.12 to 7.3.13
Actions #34

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 7.3.13 to 7.3.14
Actions #35

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 7.3.14 to 7.3.15
Actions #36

Updated by Alexis Mousset about 1 month ago

  • Status changed from New to Released
  • Regression set to No

We fixed it by adding a prefix for windows techniques

Actions

Also available in: Atom PDF