Releases: cloudposse/terraform-aws-vpc-flow-logs-s3-bucket
Releases · cloudposse/terraform-aws-vpc-flow-logs-s3-bucket
v0.15.0
Add support for bucket notifications @max-lobur (#37)
what
- Add support for bucket notifications
- Bypass all vars to log storage module
why
- To enable log collection
v0.14.2
🚀 Enhancements
Chore: Update `context.tf`; Bump Module Dependencies; Update GitHub Actions Workflows; Drop Unused Providers @korenyoni (#36)
what
- Update
context.tf
tonull-label:0.25.0
. - Bump module dependencies to latest.
- Drop unused providers.
- Run
make github/init
.
why
context.tf
is out of date (null-label:0.24.1
) andnull-label:0.25.0
is not backwards compatible withnull-label:0.24.1
, meaning chaining this module with modules atnull-label:0.25.0
or above will not work.- Module dependencies using
context.tf
withnull-label:0.24.1
need to be bumped to their latest versions, which usecontext.tf
fromnull-label:0.25.0
- Some providers are not used.
- Running
make github/init
updates all GitHub Workflows to the latest versions provided by build-harness.
$ tflint --module --enable-rule=terraform_deprecated_index --enable-rule=terraform_unused_declarations --enable-rule=terraform_documented_outputs --enable-rule=terraform_required_providers --enable-rule=terraform_unused_required_providers
2 issue(s) found:
Warning: provider 'local' is declared in required_providers but not used by the module (terraform_unused_required_providers)
on versions.tf line 5:
5: local = {
6: source = "hashicorp/local"
7: version = ">= 1.3"
8: }
Reference: https://github.com/terraform-linters/tflint/blob/v0.27.0/docs/rules/terraform_unused_required_providers.md
Warning: provider 'template' is declared in required_providers but not used by the module (terraform_unused_required_providers)
on versions.tf line 9:
9: template = {
10: source = "hashicorp/template"
11: version = ">= 2.2"
12: }
Reference: https://github.com/terraform-linters/tflint/blob/v0.27.0/docs/rules/terraform_unused_required_providers.md
references
v0.14.1
🚀 Enhancements
Fix deleted variabled @jamengual (#34)
what
- this PR #28 changed the way the arn was formatted and it does it automatically using the local
local.arn_format
and it deleted the var.arn_format variable but there were 2 references tovar.arn_format
ln the dynamic.
why
- because it fails if you use the dynamic to force SSL.
references
v0.14.0
Add custom policy variable @bwmetcalf (#33)
what
- Allow for a custom iam policy document to be passed in
why
- The current policy in this module only allows for the logs to be written to s3. It doesn't provide actions necessary
for those logs to be consumed from s3.
v0.13.0
Automatically lookup arn format. @bwmetcalf (#28)
what
- Automatically lookup arn format instead of hardcoding the partition. This is needed for use in govcloud, for example.
why
- Makes the module easier to use.
references
v0.12.2
🚀 Enhancements
Fix: Ensure Module Adheres var.allow_ssl_requests_only @korenyoni (#29)
what
- Ensure module adheres
var.allow_ssl_requests_only
by building out aForceSSLOnlyAccess
statement in the policy passed to thes3-log-storage
module
why
- Since this module creates its own policy and passes it to the
s3-log-storage
module, thes3-log-storage
module will disregardvar.allow_ssl_requests_only
.
references
🐛 Bug Fixes
Fix: Ensure Module Adheres var.allow_ssl_requests_only @korenyoni (#29)
what
- Ensure module adheres
var.allow_ssl_requests_only
by building out aForceSSLOnlyAccess
statement in the policy passed to thes3-log-storage
module
why
- Since this module creates its own policy and passes it to the
s3-log-storage
module, thes3-log-storage
module will disregardvar.allow_ssl_requests_only
.
references
v0.12.1
🚀 Enhancements
add arn format to the kms policy @rryke (#27)
currently getting:
Error: MalformedPolicyDocumentException: Policy contains a statement with one or more invalid principals.
on .terraform/modules/flow_logs.kms_key/main.tf line 1, in resource "aws_kms_key" "default":
1: resource "aws_kms_key" "default" {
what
- Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
- Use bullet points to be concise and to the point.
why
- Provide the justifications for the changes (e.g. business case).
- Describe why these changes were made (e.g. why do these commits fix the problem?)
- Use bullet points to be concise and to the point.
references
- Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
- Use
closes #123
, if this PR closes a GitHub issue#123
v0.12.0
v0.11.1
🤖 Automatic Updates
chore(deps): update terraform cloudposse/s3-log-storage/aws to v0.20.0 @renovate (#23)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-log-storage/aws (source) | terraform | minor | 0.19.0 -> 0.20.0 |
Release Notes
cloudposse/terraform-aws-s3-log-storage
v0.20.0
context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#53)
#### what - update context.tf to v0.24.1 - minimum required Terraform version bumped to 0.13.0 - readme updated, Bridgecrew compliance badges added #### why - It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below - we have dropped support for Terraform 0.12 - To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliantv0.11.0
- No changes