When I upgrade DB Connect v3.2.0 to v3.3.0 on Splunk 7.x, I get a validation error for every stanza in commands.conf and restmap.conf where there is a value for python.version. Here's an example:
Invalid key in stanza [dbxquery] in /opt/splunk/etc/apps/splunk_app_db_connect/default/commands.conf, line 3: python.version (value: python3).
Here's the full stanza:
[dbxquery]
run_in_preview = false
python.version = python3
filename = dbxquery_bridge.py
chunked = true
What's the right way to customize the stanza to run on 7.x in terms of the default vs. local folder? The way I understand the Python3 migration documentation, the python.version parameter wasn't introduced until 8.0. If that's the case then I need to remove the parameter, but the Clear a setting technique doesn't seem to work. I get validation errors for both the empty value and the python3 value:
[dbxquery]
python.version =
[filterdbxsourcetype]
python.version =
Invalid key in stanza [dbxquery] in /opt/splunk/etc/apps/splunk_app_db_connect/local/commands.conf, line 2: python.version (value: )
Invalid key in stanza [dbxquery] in /opt/splunk/etc/apps/splunk_app_db_connect/default/commands.conf, line 3: python.version (value: python3).
I don't have to hack the copy in the default folder, do I? That approach obviously goes against the best practice of only customizing files in the local folder.
