Actions
Bug #22620
closedMissleading use of parameter variable_name in method condition_from_variable_match
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
I was trying to define a condition according to a property, so I use as variable_name parameter: ${node.properties[..][..]}
I get an error :
E| error test_condition_var Check if Ntp Configurati| ntp_config_in_use Create the condition ntp_config_in_use_{true,false} from the result of regex: /Ntp/ on variable Ntp could not be repaired
In fact, we don't have to use the syntax ${...}
since it is the name of the variable, it should be explicit in the documentation
Updated by Elaad FURREEDAN over 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/1387
Updated by Anonymous over 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset ncf|8f1ca271f8a6b030479253062a2d8772c963b0f5.
Updated by Félix DALLIDET over 1 year ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.6 and 7.3.1 which were released today.
Actions