-
-
Notifications
You must be signed in to change notification settings - Fork 237
fix: Defined dependencies for aws_ram_resource_share_accepter and aws_route #144
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
fix: Defined dependencies for aws_ram_resource_share_accepter and aws_route #144
Conversation
…t_gateway_vpc_attachment<-aws_route.this
@antonbabenko I don't see a way to ask for review here. The previous PR I had expired and got closed automatically :) |
any chance to review it? |
spam to keep bot from closing it |
This PR has been automatically marked as stale because it has been open 30 days |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small comments before we can merge it and move on further.
## [2.13.1](v2.13.0...v2.13.1) (2025-09-23) ### Bug Fixes * Defined dependencies for aws_ram_resource_share_accepter and aws_route ([#144](#144)) ([6a09286](6a09286))
This PR is included in version 2.13.1 🎉 |
Description
Defined dependencies: aws_ram_resource_share_accepter<-aws_ec2_transit_gateway_vpc_attachment<-aws_route.this
Motivation and Context
I was using this module to wire the transit gateway from one account to another (peer account) and the code fails to create route table in peer VPC because of the missing resource ordering. It creates route table in peering VPC before accepting the RAM share and TGW attachment to the VPC.
Terragrunt apply fails with the following error:
Breaking Changes
No.
How Has This Been Tested?
pre-commit run -a
on my pull request