View Issue Details

IDProjectCategoryView StatusLast Update
0001454bareos-coredirectorpublic2022-05-05 14:22
Reportermdc Assigned To 
Status newResolutionopen 
Platformx86_64OSCentOSOS Versionstream 8
Product Version21.1.2 
Summary0001454: Add config option to let run scripts only on an specific job level
DescriptionUntil now, an script can only runs before or after an job. But for some jobs like backup an PostgreSQL database using your add on an third situation will occurs.
An script run before an full backup job is needed, which removes the old wal archive files.
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action




2022-05-03 10:42

developer   ~0004586

Maybe you want to use the Characters substitution flag and use that to determine which kind of job you are running
%l = Job Level


2022-05-04 07:12

reporter   ~0004588

This have I done as an workaround, but this needs an wrapper script to call the "real" script/application.


2022-05-05 14:00

developer   ~0004596

Maybe you are encline to propose a PR for that option ?


2022-05-05 14:22

reporter   ~0004598

I think it will needs deeper internal changes and I don't have deeper code knowledge.
So my idea is, because for me an workaround exists, that the ticket can be put with an low priority on the "which list".

Issue History

Date Modified Username Field Change
2022-05-03 07:02 mdc New Issue
2022-05-03 10:42 bruno-at-bareos Note Added: 0004586
2022-05-04 07:12 mdc Note Added: 0004588
2022-05-05 14:00 bruno-at-bareos Note Added: 0004596
2022-05-05 14:22 mdc Note Added: 0004598