Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MediaConvert adapter has direct_output_lookup config, to avoid using CloudWatch #102

Merged
merged 2 commits into from
Apr 28, 2022

Conversation

jrochkind
Copy link
Contributor

MediaConvert adapter has direct_output_lookup config

To calculate output directly from the MediaConvert Job object, without requiring the CloudWatch logs.

(Also includes a commit that renamed some methods/variables for clarity, and added inline comments.)

All the info we were returning is there EXCEPT the actual output URLs. Sufficient info is there to calculate/predict the output URLs though -- I have done that for HLS. I believe it should be do-able for other formats too, but I am no
t familiar with them to figure out what they should be, so for NOW the URL calculation is only there for HLS. (If it's important, I could try to familiarize myself with the others and how the adapter currently handles them and try to match them without CloudWatch too? Not sure what other outputs are in any actual use at present, if any?)

This logic makes some assumptions, like that hteres only one input file and only one output group -- but I think such assumptions were already being made, and the adapter at current is incapable of violating them. It does potentiall
y introduce some additional fragility though.

@cla-bot cla-bot bot added the cla-signed label Apr 19, 2022
@jrochkind
Copy link
Contributor Author

circleci does not seem to be kicking off, I don't know how to fix it. :(

@jrochkind jrochkind force-pushed the alternate_output_determination branch from 74c4782 to 2578918 Compare April 27, 2022 21:08
To calculate output directly from the MediaConvert Job object, without requiring the CloudWatch logs.

All the info we were returning is there EXCEPT the actual output URLs. Sufficient info is there to calculate/predict the output URLs though -- I have done that for HLS. I believe it should be do-able for other formats too, but I am not familiar with them to figure out what they should be, so for NOW the URL calculation is only there for HLS. (If it's important, I could try to familiarize myself with the others and how the adapter currently handles them and try to match them without CloudWatch too? Not sure what other outputs are in any actual use at present, if any?)

This logic makes some assumptions, like that hteres only one input file and only one output group -- but I _think_ such assumptions were already being made, and the adapter at current is incapable of violating them. It does potentially introduce some additional fragility though.
@jrochkind jrochkind force-pushed the alternate_output_determination branch from 2578918 to 2a86c51 Compare April 27, 2022 21:12
Copy link
Member

@mbklein mbklein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻

@mbklein
Copy link
Member

mbklein commented Apr 28, 2022

I approved this because the PR looks good and the tests passed on my system. It would be great to get them passing in CI as well.

@jrochkind
Copy link
Contributor Author

I believe @cjcolvar can make them run somehow. Pretty please then we'll merge after pass?

@cjcolvar cjcolvar merged commit ae501a3 into main Apr 28, 2022
@cjcolvar cjcolvar deleted the alternate_output_determination branch April 28, 2022 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants