v0.7.0

This release brings support for Next.js image optimization 📸.
No extra config is needed, simply update the Terraform module and the tf-next package to the latest version!
Check out our example for more information: Next image component example

You can always opt-out from creating resources for image optimization by setting create_image_optimization = false.

Changelog

Terraform module

• Adds support for next/image component (#28, #51)
• Refactoring: Outsources a previously private Terraform module, that is now used across multiple projects. Is now available here: NPM Download Terraform module
  (#41)

tf-next (0.5.0)

• Adds support for next/image component (#28, #51)

Proxy (0.5.0)

• Internal refactoring which changes the way the module is bundled. No feature changes (#43)

Deploy trigger (0.2.0)

• Internal refactoring which changes the way the module is bundled. No feature changes (#43)

v0.6.2

Changelog

Terraform module

• Bump internal module version of terraform-aws-modules/lambda/aws: 1.31.0 -> 1.34.0
  This should fix an issue when performing a direct upgrade from v0.3.0 to v0.6.x

v0.6.1

Changelog

Terraform module

• Fix: Correctly propagate the permissions boundary (lambda_role_permissions_boundary) to all Lambda & Lambda@Edge functions (#38)

tf-next (0.4.1)

• Fix: Request cookie header should be semi-colon delimitated (#39)

v0.6.0

Changelog

⚠️ Breaking Changes ⚠️

You need to update the tf-next package to the latest version in order to use it with the v0.6.0 release.

npm upgrade tf-next@latest   # npm
yarn upgrade tf-next@latest  # yarn

Terraform module

• Upgrade to API Gateway Payload V2.0 (#29, #31)
  This is only an upgrade of the internally API used by Lambda and API Gateway (Not the resource itself, since we already use API Gateway V2). See this guide for a detailed look at the differences between the V1.0 and V2.0 format.
  It fixes a bug where no multi-value headers could be sent by a SSR or API page.
• Sends an error message when you try to use the Terraform module together with an old version of tf-next (#5, #37)
• Upgrades proxy component to v0.4.0

tf-next (0.4.0)

• Adds a version number to the config file, so that the Terraform module is able to warn about a possible version mismatch (#5, #37)

Proxy (0.4.0)

• Fix to handle resource handle type properly

v0.5.3

Changelog

Terraform module

• Fix: Pass permissions boundary to edge proxy lambda (#35)

v0.5.2

Changelog

Terraform module

• Adds tags variable to set tags on supported AWS resources (#34)
• Adds lambda_role_permissions_boundary variable for setting a permission boundary for the Lambda role (#33)

v0.5.1

Changelog

Terraform module

• Adds cloudfront_hosted_zone_id output (#30).

v0.5.0

Happy New Year! 🍾
With this release we bring native support for redirects in Next.js.

Changelog

Proxy (0.3.0)

• Adds ability to handle redirects (#10, #24).

tf-next (0.3.0)

• The build tool got a new name, now it is simply tf-next instead of @dealmore/terraform-next-build.
  For backwards compatibility we plan to release new versions to both the old and the new package name until v1.0.

• When running tf-next build we now filter out routes with the prefix _next/static/* since they are handled directly by CloudFront and will never hit the Proxy.

v0.4.0

Changelog

• Adds new example how to use custom domains.

Terraform module

• Adds ability to change the price class of the associated CloudFront distributions (cloudfront_price_class).
• Adds new option after how many days the static assets of previous deployments should be deleted from S3(expire_static_assets).
• Updates deploy trigger Lambda function to v0.1.0.

Deploy trigger

• Static routes are now cached much longer by CloudFront.
• Static routes from CloudFront now get invalidated when a new deployment is pushed.
• Updates deploy trigger Lambda function to support expiration of previous deployments.

v0.3.0

Changelog

• Adds support for Terraform v0.14 (#18)
• Drops support for Terraform v0.12