Feature Request: Allow any SRT Stream ID through AdmissionWebhooks

[bchah]

I would like to use OME with some industry standard encoders and decoders like BirdDog, AJA and Kiloview. However these units do not always support the URL-encoded format required for SRT Stream ID in OME. It is different from hardware to hardware but for example, the BirdDog X1 forces the Stream ID to all uppercase characters, and the Kiloview D350 strips any url-escaped characters from the Stream ID (like %). None of these can stream to OME, so we need to be able to support a much simpler format of Stream ID (like "abc123").

Currently if an SRT incoming or outgoing request arrives to OME, it will block the request if the Stream ID is not in the OME format.

My request is that when AdmissionWebhooks is enabled for SRT publishers, please allow any Stream ID through so we may parse the ID and provide an OME-compatible one as part of the "new_url" response. This way we can offer highly compatible SRT streaming to encoders and decoders of any kind 🙏

[dimiden]

That sounds like a great idea.

Currently, the SRT Publisher can receive the stream_id in the format vhost/app/stream, and I was planning to apply this approach to the SRT Provider soon. However, but further improving it to accept a simple plain string as the stream ID could help build a more flexible system.

I will review whether there are any side effects when applying it to the SRT Provider, and if there are no major issues, I will implement this feature.