[action] [PR:18556] Add dependency for tsa_enabled flag before populating peer config and bringing up BGP (#18556) #18721
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
Ensure BGP peer bring-up and route advertisements are done only after checking TSA status during reload
Work item tracking
Microsoft ADO (number only): 27171112
How I did it
Add dependency on tsa_enabled flag before peer configuration
How to verify it
Validate that the BGP session bring up is not complete until tsa_enabled flag is populated.
Ensure no traffic is drawn to the device when in TSA and reboot with BGP unshut.