r/aws_vpc_peering_connection_accepter: vpc_id and peer_vpc_id not set correctly for same-account peerings

[ewbankkit]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Discovered while testing #7627.
For same-account VPC peering connections the aws_vpc_peering_connection_accepter resource is not correctly setting the vpc_id and peer_vpc_id attributes.

[aeschright]

Hi @ewbankkit! Thanks for noting this. Can you attach a config that demonstrates the problem, so someone could work on it?

[ewbankkit]

@aeschright We can use the testAccAwsVPCPeeringConnectionAccepterConfigSameRegionSameAccount configuration from aws/resource_aws_vpc_peering_connection_accepter_test.go:

resource "aws_vpc" "main" {
  cidr_block = "10.0.0.0/16"
  tags = {
    Name = "test"
  }
}

resource "aws_vpc" "peer" {
  cidr_block = "10.1.0.0/16"
  tags = {
    Name = "test"
  }
}

// Requester's side of the connection.
resource "aws_vpc_peering_connection" "main" {
  vpc_id      = "${aws_vpc.main.id}"
  peer_vpc_id = "${aws_vpc.peer.id}"
  auto_accept = false
  tags = {
    Name = "test"
  }
}

// Accepter's side of the connection.
resource "aws_vpc_peering_connection_accepter" "peer" {
  vpc_peering_connection_id = "${aws_vpc_peering_connection.main.id}"
  auto_accept               = true
  tags = {
    Name = "test"
  }
}

[github-actions]

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]

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.