[Bacula-users] baculabackupreport ini variable quoting issue

[Rob G. <ro...@cr...>]

Bill, I'm adopting your baculabackupreport python script and I've found
some strange behavior.

I have copy and pasted some variables from the script into the ini file. I
didn't change many of the ones I pasted in, I more wanted to 'bookmark'
them by putting them in the ini file so I could find them easily later if I
decided to experiment with them.

The trouble I've encountered a couple times now is that sometimes the
script doesn't like the variables as originally quoted in the script.

For example, I copied over this variable, exactly as you see it here:
alwaysfailcolumn = 'jobname'    # Column to colorize for "always failing
jobs" (column name, row, none)

But now the previously correctly working script says this:

[bacula@td-bacula baculabackupreport]$
/opt/baculabackupreport/email_daily.sh
- Reading configuration overrides from config file
'/opt/baculabackupreport/my.ini', section 'DEFAULT' (if exists), and
section 'Daily'

The 'alwaysfailcolumn' name ''jobname'' not valid or not in cols2show.

It looks like the script handles the single quoted variables fine when
they're in the script itself, but tries to add them when the variable is in
the ini. The trouble goes away if I remove the single quote marks.

Even more weird, other single quoted variables copied from the ini into the
script seem to work fine (those variables are also not modified from their
default).

as an example, the script seems fine with this in the ini:
ignore_jobs_lst = ['Job1', 'Job2']
or this:
ignore_warn_on_zero_inc_jobs = 'Job1 Job2'

This isn't too difficult to work around, and once I have it set up I won't
be changing variables much at all, if ever. Still, I thought I'd bring it
to your attention as a low priority thing I found.

I have attached my ini file, just in case you think it's relevant.

Regards,
Robert Gerber
402-237-8692
ro...@cr...