Closed andres-vara closed 3 years ago
it hits get_transit_gateway_route_table_associations
anyway at least once since if status != 'associated' or status != 'disassociated':
is always true, you can replace that statement with
if True:
flag = True
existing code is not broken tho
Thanks for bringing to our attention.
There 4 possible states ('State': 'associating'|'associated'|'disassociating'|'disassociated'). The condition is to make sure we wait for the transitioning state (associating | disassociating) to a stable state (associated | disassociated). Thus, in _get_association_state function we make _get_transit_gateway_route_tableassociations API to make sure is in a stable state.
It seems removing this condition would not impact the workflow but it would add another _get_transit_gateway_route_tableassociations API to the workflow.