Releases: trussworks/terraform-aws-logs
Releases · trussworks/terraform-aws-logs
Adds force_destroy bool, defaults to false
In the scenario where during a terraform destroy you want to delete a bucket that isn't empty, force_destroy = true allows a bucket to be deleted even if objects exist in the bucket. These objects are not recoverable! The bool defaults to false.
v4.1.1: Bump github.com/gruntwork-io/terratest from 0.22.3 to 0.23.0
Bumps [github.com/gruntwork-io/terratest](https://github.com/gruntwork-io/terratest) from 0.22.3 to 0.23.0. - [Release notes](https://github.com/gruntwork-io/terratest/releases) - [Commits](https://github.com/gruntwork-io/terratest/compare/v0.22.3...v0.23.0) Signed-off-by: dependabot-preview[bot] <[email protected]>
v4.1.0
Applies the bucket policy directly to the bucket resource to fix an issue when creating a cloudtrail and logging bucket in the same terraform apply.
- Adds terratests for all supported services.
- See the Upgrade Paths notes in the README.
- terratest version bump
Terraform 0.12
- Updates to Terraform 12 syntax
- Adds Terratest plumbing
v3.5.0
fix to properly support ALB customizations (#33)
v3.4.0: Support tf 0.11 again (#31)
support tf 0.11 again
v3.3.0: Limit by multiple accounts (#30)
limit by multiple accounts
v3.2.0: Merge pull request #29 from trussworks/cg_secure_s3_bucket_to_account
Secure S3 bucket from being written to by services on different accounts
v3.1.1: Latest README
The README didn't get automatically updated. This brings it up to date.
Fixes #12 bucket_policy template errors
- Fixes #12 policy template error by removing offending syntax
- Adds better support for mixed allow flags to prevent similar errors