Skip to content

v0.13.2

Compare
Choose a tag to compare
@github-actions github-actions released this 05 Jul 18:43
· 21 commits to main since this release
030d3f3

🚀 Enhancements

chore(deps): update terraform cloudposse/label/null to v0.25.0 (main) - abandoned @renovate (#67)

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 (cloudposse/label/null)

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.

Properly output descriptors of chained modules @​Nuru (#​133)

what

  • Properly output descriptors of chained modules

why

  • Bug fix; implement intended behavior

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.25.0 (main) - abandoned @renovate (#67)

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 (cloudposse/label/null)

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.

Properly output descriptors of chained modules @​Nuru (#​133)

what

  • Properly output descriptors of chained modules

why

  • Bug fix; implement intended behavior