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

Elastic Transcoder Preset: MaxFrameRate defaults to 30, but shouldn't. #9847

Closed
tecnobrat opened this issue Nov 3, 2016 · 2 comments · Fixed by #11340
Closed

Elastic Transcoder Preset: MaxFrameRate defaults to 30, but shouldn't. #9847

tecnobrat opened this issue Nov 3, 2016 · 2 comments · Fixed by #11340

Comments

@tecnobrat
Copy link

When using a aws_elastictranscoder_preset we want to be able to set "FrameRate" to a static frame rate, and not use MaxFrameRate.

According to the AWS docs, this is accomplished by simply not passing MaxFrameRate. However terraform defaults MaxFrameRate to 30:

"max_frame_rate": &schema.Schema{
Type: schema.TypeString,
Default: "30",
Optional: true,
ForceNew: true,
},

This causes the following API error on apply:

* aws_elastictranscoder_preset.desktop_video: Error creating Elastic Transcoder Preset: ValidationException: When you specify a value for MaxFrameRate, you must also specify 'FrameRate':'Auto'. Either change the value of FrameRate or remove the MaxFrameRate object, and resubmit the request.
	status code: 400, request id: f70b50ff-a1e7-11e6-8ba6-0f0748938856

MaxFrameRate will default to 30 if you do not pass a value, according to the AWS docs. So terraform does not need to enforce this setting to be default of 30.

@svanzoest
Copy link
Contributor

svanzoest commented Jan 18, 2017

I just ran into this as well (with v0.8.2). It makes it impossible to create a preset with a constant FrameRate.

@ghost
Copy link

ghost commented Apr 17, 2020

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants