I’m planning on changing the way Jibri configuration is implemented soon. There’s a PR here and a migration guide here that I’d be interested in feedback on. This code does not break Jibris with an “old” config file: it leverages the new jitsi-metaconfig lib to first check the old configuration and, if no value is found, check the new configuration.
Soon after that PR lands, Jibri will start logging warnings if “old” configuration is being used for parameters. Some (appropriate) amount of time later, exceptions will be thrown if old configuration is present. Finally Jibri will stop checking old config locations entirely.
The type of feedback I’m looking for:
- Does the code in that branch properly respect your existing config?
- Anything in the config migration guide that can be made clearer?
The type of feedback I’m not looking for:
- Why are you doing this?
- Why didn’t you use lib XYZ?