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 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
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Currently I see creating EC2 Transit Gateway Route Table Association (tgw-rtb-0adce2d3feec543ec_tgw-attach-094dc7f1085117982): IncorrectState: tgw-attach-094dc7f1085117982 is in invalid state when initially creating the peering from resources depending on the peering.
That's because the peering has not yet been established (there is manual intervention required). Autoaccepting doesn't seem to work in my case (maybe I should research that).
However, indifferent of that it would be great to have a flag to instruct the resource to wait until the peering is complete.
Community Note
Description
Currently I see
creating EC2 Transit Gateway Route Table Association (tgw-rtb-0adce2d3feec543ec_tgw-attach-094dc7f1085117982): IncorrectState: tgw-attach-094dc7f1085117982 is in invalid state
when initially creating the peering from resources depending on the peering.That's because the peering has not yet been established (there is manual intervention required). Autoaccepting doesn't seem to work in my case (maybe I should research that).
However, indifferent of that it would be great to have a flag to instruct the resource to wait until the peering is complete.
New or Affected Resource(s)