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

Security group rules get added then removed #370

Closed
hashibot opened this issue Jun 13, 2017 · 4 comments
Closed

Security group rules get added then removed #370

hashibot opened this issue Jun 13, 2017 · 4 comments
Labels
bug Addresses a defect in current functionality. service/ec2 Issues and PRs that pertain to the ec2 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@hashibot
Copy link

This issue was originally opened by @tomstachura as hashicorp/terraform#10100. It was migrated here as part of the provider split. The original body of the issue is below.


This snippet:
resource "aws_security_group_rule" "admin" {
type = "ingress"
from_port = "${var.admin_ports[count.index]}"
to_port = "${var.admin_ports[count.index]}"
protocol = "tcp"
security_group_id = "${aws_security_group.admin.id}"
cidr_blocks = ["${var.admin_ips[count.index]}/32"]

count = "${length(var.admin_ips)}"
}

will create the 4 IPs and Ports configured when I run apply, however if I run apply again, they get removed. Then, if I run apply again, they get added, and so on.
I would of course expect that they get added and don't change.

@github-actions
Copy link

github-actions bot commented Apr 3, 2020

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 3, 2020
@RichiCoder1
Copy link

This is still happening as of terraform v0.12 and AWS provider v2.57.0

@ghost ghost removed the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 11, 2020
@github-actions
Copy link

github-actions bot commented Apr 1, 2022

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 1, 2022
@github-actions github-actions bot closed this as completed May 2, 2022
@github-actions
Copy link

github-actions bot commented Jun 2, 2022

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/ec2 Issues and PRs that pertain to the ec2 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

3 participants