You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BTW
This release is also breaking for a different reason - if one had s3_origins defined, with this patch version release, it breaks as it expects the origin_access_control_id argument. This should be released as a minor release, not a patch one
Expected Behavior
Have only one block s3_origin_config if defined
Steps to Reproduce
Create two s3_origins
Screenshots
No response
Environment
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Describe the Bug
With the release of https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/pull/319/files , a bug was introduced in line 585: https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/pull/319/files#diff-dc46acf24afd63ef8c556b77c126ccc6e578bc87e3aa09a931f33d9bf2532fbbR585 . The for_each shouldn't be based on a number of s3_origins, but rather a single block at most should be there
BTW
This release is also breaking for a different reason - if one had s3_origins defined, with this patch version release, it breaks as it expects the
origin_access_control_id
argument. This should be released as a minor release, not a patch oneExpected Behavior
Have only one block
s3_origin_config
if definedSteps to Reproduce
Create two s3_origins
Screenshots
No response
Environment
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: