Releases: cloudposse/terraform-aws-cloudfront-s3-cdn
Releases · cloudposse/terraform-aws-cloudfront-s3-cdn
v0.60.0
v0.59.0
Correct enabled behavior @syphernl (#147)
what
- Replaced the
enabled
flag withdistribution_enabled
- Corrected behavior for actual
enabled
flag to prevent from creating any resources
why
- The
enabled
input was being used to manage the distribution state, which does not match the description of "Set to false to prevent the module from creating any resources" since settingenabled
tofalse
still resulted in the CloudFront distribution and S3 bucket to be created. - The behavior is now similar to that of terraform-aws-cloudfront-cdn
v0.58.1
🚀 Enhancements
Use acm module instead of awscli @nitrocode (#145)
what
- Use acm module instead of awscli
- Kept original awscli command for posterity
why
- Why use the CLI when you can use terraform ?
references
- Closes #26
v0.58.0
Use `website_endpoint` instead of `bucket_regional_domain_name` @nitrocode (#149)
what
- Uses the bucket
website_endpoint
instead of thebucket_regional_domain_name
- The
bucket_regional_domain_name
is incorrectly documented in the hashicorp aws_cloudfront_distribution docs
why
- Fixes an issue introduced in a recent PR which drops the
-website
portion of the domain
references
- Closes #148
- Fixes previous PR https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/pull/143/files#r604661084
@syphernl has confirmed that this fixes his issue by using the feature branch as a source.
v0.57.0
Provide better description for var.origin_bucket @nitrocode (#142)
what
- Provide better description for var.origin_bucket
- Provide an example of reusing an s3 bucket in the README
why
- There's some confusion whether to define this value as the bucket to be created or to reuse an existing bucket
references
- Closes #90
v0.56.0
Set minimum protocol version to TLSv1.2_2019 @nitrocode (#144)
what
- Set minimum protocol version to TLSv1.2_2019
why
- This is the most secure option as it only supports tls 1.2 and 1.3
references
v0.55.0
Remove static bucket hack @nitrocode (#143)
This is for comments to ensure this PR doesn't break backwards compatibility.
what
- This simplifies calculating the correct bucket regional domain name using the s3 bucket's
bucket_regional_domain_name
instead of the original hack from PR #17 - I saw this output used on the official hashicorp docs for the aws_cloudfront_distribution resource
why
- This simplifies the regional domain name
- Prevents having to maintain a list of buckets with dashes
- Prevents issues related to the data source of the
aws-cli
s3 bucket - Should maintain destruction of the resources as it does before
references
- More digging down the rabbit hole in this ticket #101
v0.54.0
Remove unused template provider @nitrocode (#146)
what
- Removes the unused template provider
why
- Forgot to remove the provider in this PR #141
references
- Fully closes #139
v0.53.0
Replaced old data.template_file to use latest aws provider and tf @nitrocode (#141)
what
- Removed the old data.template_file source
why
- Use more recent providers so M1 can be used
references
- Closes #139
v0.52.0
Improve DNS-related variable descriptions @alexjurkiewicz (#137)
And add dns_alias_enabled to the README's basic example.