Project

General

Profile

Actions

Bug #16311

closed

A generic method is declared as invalid for classic/linux agent if it contais curly braces with whitspace in it

Added by Vincent MEMBRÉ almost 5 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
N/A
Category:
Web - Technique editor
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

When you create a generic method, it will be declared as not valid for cfengine agent if it contains a coupleof curly braces with only whitespaces or nothing in between.

This syntax is used to declared empty lists in CFEngine and can also appear in strings (obviously).

The method will be displayed as non compatible with classic agent in the technique editor, will be applied correclty by a directly, But reporting will be wrong, you will get an n/a report stating that the method is not valid for classic agent, breaking reporting in Rudder (two reports made, one ok, and one n/a

As a workaround empty list can be declared using the following syntax

"my_slist" slist => splitstring("","",0);
Actions #1

Updated by Vincent MEMBRÉ almost 5 years ago

Problem is when we look if a method is invalid we try to guess that we have an empty cfengine file like this

<Bunch of metadata>
bundle agent my_method (params) {

}

by looking if we match an pair of culry braces with only whitespace characters in between ({\s*}) which can happen obsiously

Actions #2

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #3

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions #4

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #5

Updated by François ARMAND over 4 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 47
Actions #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
  • Priority changed from 47 to 46
Actions #7

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
  • Priority changed from 46 to 45
Actions #8

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.20 to 797
  • Priority changed from 45 to 44
Actions #9

Updated by Benoît PECCATTE over 3 years ago

  • Target version changed from 797 to 6.1.14
  • Priority changed from 44 to 43
Actions #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #11

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #12

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #13

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #14

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #16

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #17

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #18

Updated by Alexis Mousset over 1 year ago

  • Status changed from New to Rejected
  • Priority changed from 43 to 0
  • Regression set to No

we now use explicit tags starting from 7.3, closing

Actions

Also available in: Atom PDF