v1.0.2

🚀 Enhancements

Change `policy` to `source_policy_documents` @johncblandii (#39)

what

• Use source_policy_documents instead of policy

why

• policy is combined with source_policy_documents upstream, but there is a ref to var.source_policy_documents and not the combined local.source_policy_documents so using only policy is not working
• policy is also deprecated so usage needs to be removed

references

• #31
• #14

v1.0.1

🤖 Automatic Updates

Update Terraform cloudposse/s3-log-storage/aws to v1.4.1 (main) @renovate (#34)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-log-storage/aws (source)	module	patch	1.4.0 -> 1.4.1

---

Release Notes

cloudposse/terraform-aws-s3-log-storage

v1.4.1

Compare Source

Sync .github @​max-lobur (#​89)

Rebuild '.github' dir from the template

🚀 Enhancements

Update Terraform cloudposse/s3-bucket/aws to v3.1.2 (main) @​renovate (#​91)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	3.1.1 -> 3.1.2

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v3.1.2: Fix Public Bucket Creation

Compare Source

What's Changed

• Remove reference to TF_DATA_DIR retained by mistake in #​40 by @​​Nuru in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/181
• Sync .github by @​​max-lobur in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/183
• Fix linters / Retest on AWS provider V5 by @​​max-lobur in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/188
• Fix Public Bucket Creation by @​​rankin-tr in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194

New Contributors

• @​​rankin-tr made their first contribution in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194

Full Changelog: cloudposse/terraform-aws-s3-bucket@3.1.1...3.1.2

---

🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v3.1.2 (main) @​renovate (#​91)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	3.1.1 -> 3.1.2

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v3.1.2: Fix Public Bucket Creation

Compare Source

What's Changed

• Remove reference to TF_DATA_DIR retained by mistake in #​40 by @​​Nuru in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/181
• Sync .github by @​​max-lobur in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/183
• Fix linters / Retest on AWS provider V5 by @​​max-lobur in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/188
• Fix Public Bucket Creation by @​​rankin-tr in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194

New Contributors

• @​​rankin-tr made their first contribution in https://github.com/cloudposse/terraform-aws-s3-bucket/pull/194

Full Changelog: cloudposse/terraform-aws-s3-bucket@3.1.1...3.1.2

---

---

v1.0.0

Support AWS Provider V5 @max-lobur (#30)

what

Support AWS Provider V5
Major release bc of S3 major release dependency update
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Sync github @max-lobur (#28)

Rebuild github dir from the template

git.io->cloudposse.tools update @dylanbannon (#24)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

v0.8.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#21)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.8.0

Add common SQS based log collection handles @max-lobur (#20)

what

• Add common sqs based log collection handles

why

• To follow the log storage buckets standardization initiative

references

Example PR cloudposse/terraform-aws-vpc-flow-logs-s3-bucket#37

v0.7.0

Make use of S3 bucket ownership @max-lobur (#18)

Inherit cloudposse/terraform-aws-s3-log-storage#61

v0.6.1

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.25.0 @renovate (#16)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	0.24.1 -> 0.25.0

---

Release Notes

cloudposse/terraform-null-label

v0.25.0

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @​Nuru (#​132)

#### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` #### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #​131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @​korenyoni (#​130)

#### what * Update README snippets to reflect use of Terraform Registry. #### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. #### references * N/A

Bridgecrew compliance @​Nuru (#​125)

#### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` #### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub #### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

v0.6.0

fix bug with policy generation @mcalhoun (#15)

what

• Fix a bug with the bucket IAM policy when allow_ssl_requests_only is set to true

notes

I had to update the module to calculate the bucket ARN now instead of reading it as an output from module.storage[0].bucket_arn because the latter would cause a cyclic dependency.

v0.5.0

pass allow_ssl_requests_only flag to underlying module @mcalhoun (#13)

what

• Pass the allow_ssl_requests_only flag to the underlying storage module

why

• AWS Foundation Best Practices

v0.4.0

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#9)

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 compliant