ordered_cache_behavior issue with dissimilar behaviors about terraform-aws-cloudfront HOT 8 CLOSED

v1.9.0 has been just released.

from terraform-aws-cloudfront.

This looks like a bug that should be fixed in the module if you or anyone else have time.

from terraform-aws-cloudfront.

Ah great! I wasn't going insane, I'm afraid I don't know enough TF to fix it, otherwise I would have ;)

from terraform-aws-cloudfront.

Terraform expects all elements within a list to be of the same type; that is, both objects must have the same keys present.

Reference

from terraform-aws-cloudfront.

So it could be ok for TF 0.14, with optional args. enabled.

"
From Terraform v0.14 there is experimental support for marking particular attributes as optional in an object type constraint.

To mark an attribute as optional, use the additional optional(...) modifier around its type declaration
"

So sounds like no way round it for now, not without losing ordering.

from terraform-aws-cloudfront.

Just ran into this as well. It seems that the optional experiment mentioned above might be a solution. Is this something that the module is willing to support (i.e. an experiments section) ?

from terraform-aws-cloudfront.

We can only use Terraform 0.13 features in these modules because of the wide range of users/versions. In 90% of cases, there is no need to use even those, and we can use features of 0.12.

This issue is just a bug. PR is welcome.

from terraform-aws-cloudfront.

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.

from terraform-aws-cloudfront.