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

providers/aws: Update ElasticTranscoderPreset to have default for MaxFrameRate #13422

Merged
merged 1 commit into from
Apr 7, 2017

Conversation

catsby
Copy link
Contributor

@catsby catsby commented Apr 6, 2017

Updates video.max_frame_rate attribute to supply a default of 30, matching our Docs and AWS docs:

Fixes test TestAccAWSElasticTranscoderPreset_basic

@stack72
Copy link
Contributor

stack72 commented Apr 7, 2017

@catsby as this now has a default, and is marked as ForceNew: true, will this cause any issues for some users? Do we need a State Migration for those who don't have it set?

@catsby
Copy link
Contributor Author

catsby commented Apr 7, 2017

@stack72 The API defaults it to 30. Any user omitting max_frame_rate is getting a ForceNew diff . Any user specifying max_frame_rate should see no change.

@stack72
Copy link
Contributor

stack72 commented Apr 7, 2017

@catsby nice :) LGTM then

@catsby catsby merged commit 0334fb0 into master Apr 7, 2017
@catsby catsby deleted the b-aws-elastic-transcoder-default-update branch April 7, 2017 20:53
@svanzoest
Copy link
Contributor

svanzoest commented Apr 13, 2017

@catsby This broke #9847 and undid #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:

* aws_elastictranscoder_preset.proxy: 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: 8cf3908f-207e-11e7-84a3-01d702018b22

@dcosson
Copy link
Contributor

dcosson commented Mar 30, 2018

I also ran into this problem and can't set a fixed frame rate.

Is the fix as simple as reverting this single line?

I can't tell since there's not really any context here explaining what the purpose of this PR was. Why should terraform ever have its own opinion on a default value if AWS specifically allows that value to be omitted?

@svanzoest
Copy link
Contributor

svanzoest commented Mar 30, 2018

@dcosson this is now tracked as hashicorp/terraform-provider-aws#695 will address this issue. I think the only reason it got added by terraform as it made the tests easier. See #13638 for some of the back story.

@dcosson
Copy link
Contributor

dcosson commented Mar 30, 2018

Got it, thanks for updating with the more in-depth comment.

@ghost
Copy link

ghost commented Apr 4, 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 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants