-
-
Notifications
You must be signed in to change notification settings - Fork 10
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 #31
Conversation
17b9b92
to
2a94e53
Compare
0963712
to
5ff7d06
Compare
5ff7d06
to
88fd4b2
Compare
bc9d33e
to
d26a1c9
Compare
Edited/Blocked NotificationRenovate 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. |
/terratest |
/terratest |
This pull request now has conflicts. Could you fix it @renovate[bot]? 🙏 |
This automated PR has been closed due to merge conflicts. |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
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
v2.0.1
Compare Source
🐛 Bug Fixes
Properly handle enabled = false @Nuru (#45)
what
enabled = false
why
v2.0.0
: Breaking changesCompare 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
why
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 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.
This PR has been generated by Mend Renovate. View repository job log here.