v0.15.0

AWS provider V4 Compatibility @max-lobur (#69)

what

AWS provider V4 Compatibility

why

Similar to https://github.com/cloudposse/terraform-aws-ec2-instance

v1.0.0

Support AWS provider V5

v0.14.0

🤖 Automatic Updates

chore(deps): update terraform cloudposse/security-group/aws to v2 (main) @renovate (#64)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/security-group/aws (source)	module	major	0.3.1 -> 2.2.0

---

Release Notes

cloudposse/terraform-aws-security-group (cloudposse/security-group/aws)

v2.2.0

Compare Source

`.editorconfig` Typo @​milldr (#​50)

what

fixed intent typo

why

should be spelled "indent"

references

https://cloudposse.slack.com/archives/C01EY65H1PA/p1685638634845009

Sync github @​max-lobur (#​47)

Rebuild github dir from the template

v2.1.0

Compare Source

• No changes

v2.0.1

Compare Source

🐛 Bug Fixes

Properly handle enabled = false @​Nuru (#​45)

what

• Properly handle enabled = false

why

• Fixes #​43

v2.0.0: Breaking changes

Compare Source

For details about migrating from v1 to v2, read the migration documentation.

Version 1 of this module had a flaw in that it tried to create new security group rules before deleting the old ones, which the Terraform provider does not handle properly and caused most attempted changes to fail. Version 2 resolves this issue by also creating a new security group when the rules change, installing the new rules in the new security group, then changing the security group assignments. Read the README and the migration documentation for more details.

Document migration from v1 to v2 @​Nuru (#​42)

what

• Document migration from v1 to v2 of this module
• Fix #​40

why

• Serious issues exist in v1, causing v2 to have different defaults and new settings. Documentation is needed to guide users on how to upgrade while minimizing service interruptions.

references

• Closes #​40

Fixes the link for examples/complete/main.tf @​jdmedeiros (#​41)

Fixes the link for examples/complete/main.tf on the README.md file.

v1.0.1

Compare Source

🐛 Bug Fixes

Handle `self = false`, add warning about `compact` and `sort` @​Nuru (#​33)

what

• Handle self = false
• Add warning about compact and sort

why

• Setting self = false in a rule (meaning the rule does not apply to the security group it is being associated with) was causing an empty rule to be created and/or causing conflicts with other rule elements. Now it works like self = null works.
• Explain some causes of the dreaded "Invalid for_each argument" error and what to do to fix it.

references

• https://github.com/hashicorp/terraform/issues/31035
• https://github.com/hashicorp/terraform/issues/30937#issuecomment-1123089348

v1.0.0: Initial release with production Semantic Versioning

Compare Source

Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature modules.

This version is functionally equivalent to v0.4.3. The only differences are to the support framework (for things like developing and testing the module).

git.io->cloudposse.tools update and test framework update @​dylanbannon (#​32)

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

Rename the exported `security-group-inputs` file to `security-group-variables` @​aknysh (#​31)

what

• Rename the exported security-group-inputs.tf file to security-group-variables.tf

why

• Standardize on file names with variables for specific resources.
  For example, we have spotinst-variables.tf for Spot, security-group-variables.tf for SG, etc.

v0.4.3

Compare Source

Update recommended inputs and outputs @​Nuru (#​26)

what

• Update recommended inputs and outputs

why

• Changes based on experience implementing several modules

🚀 Enhancements

Rename the exported `security_group_inputs.tf` file to `security-group-inputs.tf` @​aknysh (#​30)

what

• Rename the exported security_group_inputs.tf file to security-group-inputs.tf
• Update GitHub workflows and LICENSE

why

• Our naming convention is to use kebab-case for all files. Having a file in snake_case (after adding it to a repo) together with all the other files in kebab-case in the same repo does not look correct
• Keep up to date

v0.4.2

Compare Source

🐛 Bug Fixes

Correctly extract security group name for tags @​Nuru (#​25)

what

• Correctly extract security group name from var.security_group_name list when setting tags

why

• Type mismatch error otherwise

v0.4.1

Compare Source

🐛 Bug Fixes

Fix bad markup (unclosed `details` block) in README.yaml @​Nuru (#​24)

what

• Fix bad markup (unclosed details block) in README.yaml

why

• Incorrectly hides most of README

v0.4.0: New Standards, Breaking Changes

Compare Source

This release makes no attempt at backward compatibility with earlier versions.
It puts forth some new Cloud Posse standards. See details below.

As a major overhaul, it likely has bugs. It may have breaking changes in the near future as we discover design issues. However, the intention is to get this module stabilized and provide a consistent interface moving forward.

This module requires Terraform version 0.14 or later due to numerous issues in Terraform 0.13.

🚀 Enhancements

Overhaul Module to New Standards @​Nuru (#​17) (click to see details)

what

• Input use_name_prefix replaced with create_before_destroy. Previously, create_before_destroy was always set to true but of course that fails if you are not using a name prefix, because the names must be unique. Now the name is automatically a prefix if create_before_destroy is true and not if it is not.
• Input security_group_enabled renamed to create_security_group. Whether the security group is created or not, it will be enabled, and setting security_group_enabled to false does not disable the entire module, even though the module is named "security-group", which makes the old name terribly confusing. The new name is more descriptive.
• Input id renamed to target_security_group_id. Again id by itself is too vague. Converted to list to conform to new standard pattern that optional inputs which are used in conditionals are passed as list elements. See Hashicorp recommendation
• Added a security_group_name input, which, if set, will set the security group name. If not set, name will be derived from null-label. Because the security group name must be unique within an account, we should provide some way for people to set/override it other than forcing them to create a customized null-label.
• As a convenience, added rule_matrix . Many of our modules allow us...

v0.13.3

🚀 Enhancements

Update context.tf @cloudpossebot (#68)

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.

🤖 Automatic Updates

Update context.tf @cloudpossebot (#68)

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

🚀 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

---

v0.13.1

🚀 Enhancements

chore(deps): update terraform cloudposse/key-pair/aws to v0.19.0 (main) @renovate (#61)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/key-pair/aws (source)	module	minor	0.18.2 -> 0.19.0

---

Release Notes

cloudposse/terraform-aws-key-pair (cloudposse/key-pair/aws)

v0.19.0

Compare Source

Support AWS Provider V5 @​max-lobur (#​75)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

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

Sync github @​max-lobur (#​73)

Rebuild github dir from the template

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

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

Compare Source

🚀 Enhancements

Update to get rid of sensitive file warning from terraform @​brunzefb (#​69)

what

• Updated to local_sensitive_file resource, changed provider versions.

why

• This removes a terraform warning

---

🤖 Automatic Updates

chore(deps): update terraform cloudposse/key-pair/aws to v0.19.0 (main) @renovate (#61)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/key-pair/aws (source)	module	minor	0.18.2 -> 0.19.0

---

Release Notes

cloudposse/terraform-aws-key-pair (cloudposse/key-pair/aws)

v0.19.0

Compare Source

Support AWS Provider V5 @​max-lobur (#​75)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

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

Sync github @​max-lobur (#​73)

Rebuild github dir from the template

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

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

Compare Source

🚀 Enhancements

Update to get rid of sensitive file warning from terraform @​brunzefb (#​69)

what

• Updated to local_sensitive_file resource, changed provider versions.

why

• This removes a terraform warning

---

v0.13.0

AWS Provider V5 compatibility
Update subnets data source

v0.12.1

🤖 Automatic Updates

chore(deps): update terraform cloudposse/key-pair/aws to v0.18.2 @renovate (#33)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/key-pair/aws (source)	module	patch	0.18.0 -> 0.18.2

---

Release Notes

cloudposse/terraform-aws-key-pair

v0.18.2

Compare Source

🤖 Automatic Updates

Update context.tf @​cloudpossebot (#​66)

#### 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.18.1

Compare Source

🚀 Enhancements

Fix: module enablement; Import Key Test @​korenyoni (#​65)

#### what * Ensure module adheres `var.enabled` * fix tests and ensure `examples_import_key_test` is run in test suite #### why * Resources were created even when `var.enabled` was `false` #### references * Issue identified in https://github.com/cloudposse/terraform-aws-components/pull/340

#### 🐛 Bug Fixes

Fix: module enablement; Import Key Test @​korenyoni (#​65)

#### what * Ensure module adheres `var.enabled` * fix tests and ensure `examples_import_key_test` is run in test suite #### why * Resources were created even when `var.enabled` was `false` #### references * Issue identified in https://github.com/cloudposse/terraform-aws-components/pull/340

---

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.12.0 Unstable Pre-Release

We are revising and standardizing our handling of security groups and security group rules across all our Terraform modules. This is an early attempt with significant breaking changes. We will make further breaking changes soon, so using this version is not recommended.

feat: use security-group module instead of resource @SweetOps (#31)

what

• use security-group module instead of resource
• update tests

why

• more flexible than current implementation
• bring configuration of security group/rules to one standard

references

• CPCO-409

v0.11.6

🤖 Automatic Updates

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

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