Closed victorges closed 1 year ago
Sounds good! Not sure if it applies in this case, but let's keep in mind that we may be increasing attack surface by adding indirect dependencies to go-livepeer, when working on new go-tools features.
@cyberj0g that makes sense! I hadn't thought of that.
One thing I could do is just implement this as a package in the catalyst-api
repository instead, which will be the only one using this at first anyway. Then if we ever want to use it in other projects we can move it here and deal with the extra indirect dep on go-livepeer (which might as well be the project wanting to use it).
Wdyt?
Initial implementation should include AWS MediaConvert as an implementation.
type Provider interface { Transcode(req UploadVODRequest, progress func(float64)) (TranscodeStatusCompletedMessage, error) }