-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[regression] providers/aws: Setting MaxFrameRate on ElasticTranscoderPreset breaks fixed frame rate #695
Comments
Also encountered this when declaring a fixed frame rate and no max frame rate:
|
Re-adding my reply to @catsby from hashicorp/terraform#13638 for background, as that got lost in the transfer of the repo.
Correct. Just for reference I am setting the FrameRate to
Exactly.
Yes, that is it and if you read the docs carefully, it states that as well.
MaxFrameRate only applies to |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This issue was originally opened by @svanzoest as hashicorp/terraform#13638. It was migrated here as part of the provider split. The original body of the issue is below.
@catsby hashicorp/terraform#13422 broke hashicorp/terraform#9847 and undid hashicorp/terraform#11340, I can no longer set a preset with a fixed frame rate in 0.9.3, this was the reason the default was removed in the first place.
I now get:
The text was updated successfully, but these errors were encountered: