Actions
Bug #12535
closed
Variable expansion in cron technique
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
-
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
46
Name check:
Fix check:
Regression:
Description
If I use a "generic variable definition" in a new cron entry, it is not expanded.
For example, this:
/usr/bin/barman backup ${generic_variable_definition.barmanhostname} >/dev/null 2>&1
results in a file containing:
/usr/bin/barman backup ${generic_variable_definition.barmanhostname} >/dev/null 2>&1
instead of, for example:
/usr/bin/barman backup test.local >/dev/null 2>&1
Updated by 
Updated by 
Updated by
Actions