Releases: byu-oit/terraform-aws-postman-test-lambda
v6.0.0
Breaking Change: Requires Terraform AWS Provider version >= 5.26 (to access a Lambda runtime that isn't EOL).
What's Changed
- use oidc for gha aws configuration by @HayLowry in #76
- bump lambda runtime to
nodejs20
by @joshgubler in #78 - State new AWS provider requirement (v5.26) in README by @GaryGSC in #79
New Contributors
Full Changelog: v5.0.3...v6.0.0
v5.0.3
Resolves an error during terraform apply
due to AWS changing default functionality of S3 ACLs.
https://aws.amazon.com/blogs/aws/heads-up-amazon-s3-security-changes-are-coming-in-april-of-2023/
v5.0.2
Bump dependency
v5.0.1
Bump dependencies
v5.0.0
Breaking change: we now require Terraform version 1.3.0
or above, and AWS provider version 4.0.0
or above.
This is a continuation of the work done to clean up warnings in #65. We discovered that we had to move to AWS provider 4.0.0 to resolve some remaining warnings.
What's Changed
Full Changelog: v4.0.1...v5.0.0
v4.0.1
What's Changed
Note
This update may initially generate some noise in Terraform plans as it "creates" a number of S3 resources. The resources it creates are equivalent to what we were already using, hence the patch release.
Full Changelog: v4.0.0...v4.0.1
v4.0.0
This update primarily bumps the Lambda runtime to nodejs16.x
.
It's a major version update due to the requirement that the AWS provider be recent (and by extension, the TF version). Apart from updating those versions, no code changes should be necessary.
Specifically, we require Terraform version 1.0.0
or above, and AWS provider version 3.75.2
or above.
For more details, see #58.
v3.2.4
Apply log_retention_in_days
to the S3 logging bucket. (Previously, this variable only applied to the CloudWatch log group. The S3 bucket was hard coded at 120 days.)