Option to provide alternative router.db file for scripts usage
ecm75 opened this issue · comments
It would be very nice to have the possibility to provide an alternative router database file/sql to use the script feature for special use cases, maybe even providing a different oxidized config would be very nice.
Maybe this is already possible using the library feature, but due to the lack of documentation I was not able to find out...
If you specify model name and auth details in CLI, you maybe able to login to device without it being in oxidized proper.
But it wouldn't be hard to pass arbitrary config options, like new CSV file via CLI arguments, it is not supported now though.