topic Re: python.version in transforms.conf gets overwritten if you edit transform via gui in Knowledge Management

python.version in transforms.conf gets overwritten if you edit transform via gui

anachronism — Wed, 29 Jul 2020 17:25:33 GMT

Hi,

I have an external lookup I've written - and to future proof it I've written it for python3.

I have put python. version = python3 in the local transforms.conf, but if I edit the transform via the GUI that setting disappears and it without it there it reverts back to python2 as default and fails. I guess this _could_ go into default - but is there a cleaner way to do this? (In testing I can put the python version in the system.conf - but I won't be able to do that in prod 😞 ).

So much for future-proofing :(:

Running 8.0.5.

Re: python.version in transforms.conf gets overwritten if you edit transform via gui

richgalloway — Wed, 29 Jul 2020 18:30:36 GMT

Every setting that ships with the app should go in default. Leave local for local customizations.

Re: python.version in transforms.conf gets overwritten if you edit transform via gui

anachronism — Wed, 29 Jul 2020 20:28:05 GMT

I kind of agree with that - but the software is buggy and Splunk don’t want to hear about bugs from people without support contracts (at the moment I don’t have one/access to my companies one). Shame.