v0.14.3

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.25.0 @renovate (#38)

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

🤖 Automatic Updates

Update context.tf @cloudpossebot (#39)

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

🚀 Enhancements

Updates SNS_Topic Name @Benbentwo (#37)

what

• Updates sns_topic name
  From CloudTrailBreach-threshold-alerts to ${namespace}-${env}-${stage}-cloudwatch-cloudtrail-breach

why

• follow naming convention

v0.14.0

Fix: Disable non-CMK for SNS, Create CMK with Sufficient Resource-based Policy to Allow Cloudwatch to Publish to SNS @korenyoni (#36)

what

• Disable use of amazon-managed KMS key
• Use user-supplied CMK if var.kms_master_key_id is not null
• If var.kms_master_key_id is null, create a CMK for SNS topic for encryption of CloudTrailTrailBreach SNS topic and allow CloudWatch to encrypt messages published to the SNS topic.

why

• The SNS topic must be encrypted with a KMS key that allows the CloudWatch service to use it. Messages will fail to be published when using the amazon-managed default KMS key for SNS.

references

• cloudposse/terraform-aws-security-hub#20

v0.13.0

fix conditional logic @mcalhoun (#32)

what

• Fix the conditional logic for the aws_sns_topic_policy
• Update to allow the alarm to be named
• Update the catalog to reflect other changes

why

• The current logic is incorrect

v0.12.0

Adding yaml catalog @jamengual (#31)

what

• Adding config_yaml module compatibility
• Change metrics to catalog

why

• To make it easy to load big catalog of metric filters and alerts
• To make the alerts and metrics fully configurable

v0.11.0

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

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

v0.10.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#27)

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

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#29)

what

• update context.tf to v0.23.0
• 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
• 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

v0.9.1

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#28)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates