Releases: cloudposse/terraform-aws-cloudfront-s3-cdn
Releases · cloudposse/terraform-aws-cloudfront-s3-cdn
0.3.4
what
Changing the way bucket_name is populated in locals. Deriving the name from the s3 bucket resource attribute, instead of the s3 bucket argument.
why
S3 bucket attributes only exist after a resource has been made, currently S3 bucket resource arguments are used to populated a local. This change will make sure that the local.bucket falls back to var.origin_bucket. Without this change the datasource aws_s3_bucket.selected will try to use a bucket name which has not been created yet.
references
- closes #31
0.3.3 Fix S3 regional domain name resolution
what
- Fix S3 regional domain name resolution
why
- Regional domain name resolution was playing was not working for some deployments
- closes #18
0.3.2: Update README.yaml (#30)
* Update README.yaml * Update README.yaml
0.3.1
what:
- Add forwarded headers so that s3 bucket can identify origins
why
- Required for S3 origin
references
0.3.0
0.2.2
0.2.1: Migrate to README.yaml format (#19)
* Migrate to README.yaml format * Fix descriptions
0.2.0: Added optional regional s3 endpoint. Added Example (#17)
* Added the ability to specify a regional endpoint. Updated README. Created working example. * Added output in example that provided instructions for beginners * Added origin_force_destroy to all s3 buckets so that the module can be destroyed if required. * Fixed another destruction issue. * Updated for consistency * Changed the 'static' bucket * added variable for static_s3_bucket