Fix Version/s: None
Kian-Tat Lim pointed out that inflection was included by moto, but it no longer is (https://github.com/conda-forge/moto-feedstock/commit/8df708bc37c0a0bcf865d04c4a71ccc94fabea12#diff-f3725a55bf339595bf865fec73bda8ac99f283b0810c205442021f29c06eea9a). This breaks bps_config.py (https://github.com/lsst/ctrl_bps/blob/master/python/lsst/ctrl/bps/bps_config.py#L35).
Besides being a very temporary workaround that doesn't work for all situations, the above has brought up bigger discussions about what should actually be supported in the config. So, going to roll back the BPS config changes that checked various casing (snake case vs camel case vs lower case...) to requiring the keys used in submit yaml to exactly match those expected by bps or being used as variables in other submit values. Whether to make the submit yaml more flexible will be postponed to the larger bps config rewrite ticket (DM-31245)
Sergey Padolski I looked around in the PanDA idf config and plugin. There's a "runner_command" in both. As far as I can tell without testing this should still work, but does not match the casing style of all the other config values. Do you want me to change it in this ticket to runnerCommand or leave it for you to maybe change in a different PanDA specific ticket?
thanks Michelle Gower, it will be nice it you could replace "runner_command" to match the style.
I found a few other and changed them too. I pushed the changes. Let me know how it looks and if I can merge it.
The test was successfully submitted and the first task has finished. Fine with me to merge.
Rolled back changes. Whether to make BpsConfig more flexible in key lookup is postponed until general rewrite in another ticket.