v0.37.0

Add custom header block into distribution origin block @byron-hom (#108)

what

• add custom_origin_headers variable

• Updated README.md

• Update variables.tf

• Update main.tf

• Updated README.md

• Executed 'terraform fmt'

why

Use case : LambdaEdge does not allow environment variables, so if you want use multiple distributions to call same lambdaEdge function you can use a custom_headers block into distribution to pass some variables that the lambda function can read and execute some logic depends of a distribution.

references

https://stackoverflow.com/questions/54828808/aws-lambdaedge-nodejs-environment-variables-are-not-supported#:~:text=Environment%20variables%20are%20not%20supported%20by%20Lambda%40Edge%20as%20specified,with%20CloudFront%20Origin%20Custom%20Headers.

v0.36.0

make origin_ssl_protocols configurable @juliusdanielherreraglomm (#112)

what

• This change allows you to configure the origin_ssl_protocols parameter
  of the aws_cloudfront_distribution terraform resource. If this
  parameter is not configured explicitly, the old default is kept.

why

• This is just for making the module more flexible.

references

• N/A

v0.35.0

Adds explicit DNS alias _enabled flag + context.tf upgrade @Gowiem (#103)

what

• Adds var.dns_alias_enabled variable for enforcing explicit opt-in to the CDN DNS Alias.
• Upgrades to context.tf pattern

why

• The dns_alias_enabled flag is to get around an issue similar to cloudposse/terraform-aws-elasticsearch#73.
• context.tf upgrade to follow with the common Cloud Posse pattern.

references

• Relevant thread on dns_alias_enabled in SweetOps: https://sweetops.slack.com/archives/CB6GHNLG0/p1600294860394500

v0.34.1

use minimum versions for provider pinning @woz5999 (#100)

what

set minimum versions for providers without pinning to a specific major version

why

the current method makes it very difficult to maintain or upgrade consistent provider versions within a project

references

https://www.terraform.io/docs/configuration/provider-requirements.html#best-practices-for-provider-versions

v0.34.0

Adding versioning to S3 origin bucket @hawkesnc (#91)

what

• This change allows you to turn on versioning for objects in the bucket

why

• For building static websites, we require the use of s3+cdn that this module provides. However, in some instances, we would like to ability to roll back to a previous version.
• Since this is meant for a "dev" like environment, we set the cdn ttl to very low to pull objects back from the s3 bucket.
• The reason we use the CDN is to support TLS since s3 does not.

references

• N/A

v0.33.0

Updated dependency module versions to latest @vamshisiddarth (#97)

what

• Updated dependency modules to latest to support terraform 0.13.0

why

• Updated the dependency modules since they are not updated and facing error when using with Terraform 0.13.0

Dependency modules and versions:

• logs -> 0.13.1
• dns -> 0.8.0

v0.32.0

Additional TF 0.13 Fixes @osterman (#98)

what

• upgrade chatops
• add automatic releasing
• upgrade to go modules
• update any version pinning
• (locally verififed) no terraform init errors using cli

why

• Support Terraform 0.13

0.31.1: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#94)

## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

0.31.0

[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.30.0: Output the ARN of the Origin S3 Bucket (#81)

* Output the ARN of the Origin S3 Bucket

This is useful in cases where a policy is created a CI/CD user or role,
which needs access to the Origin S3 Bucket in order to add content.

* Updated README.md

* Update outputs.tf

* Updated README.md

* Executed 'terraform fmt'

Co-authored-by: Matt Gowie <[email protected]>
Co-authored-by: actions-bot <[email protected]>
Co-authored-by: nitro <[email protected]>
Co-authored-by: Erik Osterman <[email protected]>