chore(deps): update terraform cloudposse/security-group/aws to v2

renovate[bot] commented 1 year ago

This PR contains the following updates:

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

Release Notes

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

### [`v2.2.0`](https://togithub.com/cloudposse/terraform-aws-security-group/releases/tag/2.2.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-security-group/compare/2.1.0...2.2.0)

`.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`](https://togithub.com/cloudposse/terraform-aws-security-group/releases/tag/2.1.0) [Compare Source](https://togithub.com/cloudposse/terraform-aws-security-group/compare/2.0.1...2.1.0) - No changes ### [`v2.0.1`](https://togithub.com/cloudposse/terraform-aws-security-group/releases/tag/2.0.1) [Compare Source](https://togithub.com/cloudposse/terraform-aws-security-group/compare/2.0.0...2.0.1) ##### 🐛 Bug Fixes

Properly handle enabled = false @Nuru (#45)

##### what * Properly handle `enabled = false` ##### why * Fixes #43

### [`v2.0.0`](https://togithub.com/cloudposse/terraform-aws-security-group/releases/tag/2.0.0): Breaking changes [Compare Source](https://togithub.com/cloudposse/terraform-aws-security-group/compare/1.0.1...2.0.0) For details about migrating from v1 to v2, read the [migration documentation](https://togithub.com/cloudposse/terraform-aws-security-group/blob/master/docs/migration-v1-v2.md). 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](https://togithub.com/cloudposse/terraform-aws-security-group/issues/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](https://togithub.com/cloudposse/terraform-aws-security-group/issues/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`](https://togithub.com/cloudposse/terraform-aws-security-group/releases/tag/1.0.1) [Compare Source](https://togithub.com/cloudposse/terraform-aws-security-group/compare/1.0.0...1.0.1) ##### 🐛 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://togithub.com/hashicorp/terraform/issues/31035) - [https://github.com/hashicorp/terraform/issues/30937#issuecomment-1123089348](https://togithub.com/hashicorp/terraform/issues/30937#issuecomment-1123089348)

### [`v1.0.0`](https://togithub.com/cloudposse/terraform-aws-security-group/releases/tag/1.0.0): Initial release with production Semantic Versioning [Compare Source](https://togithub.com/cloudposse/terraform-aws-security-group/compare/0.4.3...1.0.0) Initial release with [production Semantic Versioning](https://semver.org/#spec-item-5), 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.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 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 Mend Renovate. View repository job log here.

renovate[bot] commented 8 months ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

hans-d commented 8 months ago

/terratest

mergify[bot] commented 7 months ago

/terratest

mergify[bot] commented 7 months ago

💥 This pull request now has conflicts. Could you fix it @renovate[bot]? 🙏

mergify[bot] commented 7 months ago

This automated PR was closed due to merge conflicts.

renovate[bot] commented 7 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

cloudposse / terraform-aws-eks-node-group