provider/aws: Add support for CustomOrigin timeouts to aws_cloudfront_distribution

[stack72]

Currently, any changes / deletions to aws_cloudfront resources with a custom_origin are completely broken

aws_cloudfront_distribution.custom_distribution: Destroying... (ID: EC5N584ZA1U1D)
Error applying plan:

1 error(s) occurred:

* aws_cloudfront_distribution.custom_distribution (destroy): 1 error(s) occurred:

* aws_cloudfront_distribution.custom_distribution: IllegalUpdate: OriginReadTimeout is required for updates.
	status code: 400, request id: dff72b5b-2a2a-11e7-8c7e-b353bd2f7989

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

I have decided that it is better to fix the error and let the users see the change than to hide it via a state migration

[mbfrahry]

This patch will fix 6 failing TestAccAWSCloudFrontDistribution tests

[fourseven]

We've run into this too. I'm guessing that AWS has changed an API without making it backwards compatible, and would prefer to update my terraform files than have a hidden state migration occur to remedy this, even if it's another terraform release away.

[rbnunes]

Is this live on the latest release? I cannot still apply changes. I either get invalid or unknown key: origin_read_timeout or IllegalUpdate: OriginReadTimeout is required for updates.

[stack72]

Hi @rbnunes

This will not be released until 0.9.5

Paul

[ghost]

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.