@bss-dmitry-shmakov is this related to #24677 and #36761 ?

no we don't use transit gateway and it's not a cross account issue. I suspect it is because peering connections are somewhere represented by unsorted array and the terraform finds a 'diff' to update something that doesn't need to be updated, because of the order is different when it reads them back after it created them. Although we have specific names to resources like resource "aws_vpc_peering_connection" "to-ireland-eks" so I don't think it should get confused which peering defined in our manifests is which one in aws... it seems to reshuffle their names every time we run, as if it wants to rename their tags to one another, for no reason. Also it tries to remove its own tag "Accepted by Terraform" all the time, despite tag is being created as part of the run.

from terraform-provider-aws.

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

from terraform-provider-aws.

@bss-dmitry-shmakov is this related to #24677 and #36761 ?

from terraform-provider-aws.