Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update terraform cloudposse/security-group/aws to v2 (release/v0) #138

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
cloudposse/security-group/aws (source) module major 1.0.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

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

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


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 becomes conflicted, 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 renovate bot requested a review from a team as a code owner March 5, 2024 00:35
@renovate renovate bot added the auto-update This PR was automatically generated label Mar 5, 2024
@renovate renovate bot requested review from a team as code owners March 5, 2024 00:35
@renovate renovate bot requested review from johncblandii and gberenice and removed request for a team March 5, 2024 00:35
Copy link
Contributor Author

renovate bot commented Mar 5, 2024

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.

@gberenice
Copy link

Already updated to cloudposse/security-group/aws v2.2.0.

@gberenice gberenice closed this Mar 5, 2024
@gberenice gberenice deleted the renovate/release/v0-cloudposse-security-group-aws-2.x branch March 5, 2024 10:06
Copy link
Contributor Author

renovate bot commented Mar 5, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-update This PR was automatically generated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant