v0.3.0 (Action needed) Migrate to AWS provider v4.x

In order to support AWS provider v4.x, this module has upgraded its use of the s3-bucket module from v0.38.0 to v0.49.0. Please see the S3 bucket migration documentation for guidance about how to upgrade this module.

Upgrade to support AWS provider v4 Jeff (@woz5999) (#11)

what

• Upgrade to support AWS provider v4
• Upgrade to latest s3 bucket module

why

• This module is currently unusable in projects using AWS provider v4

references

• closes #3

v0.2.3

🚀 Enhancements

support alternate aws partitions Jeff (@woz5999) (#10)

what

• dynamically set the aws partition when constructing ARNs

why

• hardcoded aws partitions make govcloud users sad

v0.2.2

🤖 Automatic Updates

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

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.2.1

🤖 Automatic Updates

Update context.tf Cloud Posse Bot (CI/CD) (@cloudpossebot) (#6)

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.2.0

Fix outputs validation and s3 bucket logic PePe Amengual (@jamengual) (#4)

what

• Fix output for s3 bucket when create_log_bucket not true
• Fix data s3 policy resource when create_log_bucket not true

why

• it fails when an existing bucket is passed as input

SSM Patch manager support

SSM Patch manager initial support for EC2 instances