feat: add dynamic_route_server connection type support for Transit Gateway - #214
Open
anaghajoshiibm wants to merge 1 commit into
Open
feat: add dynamic_route_server connection type support for Transit Gateway#214anaghajoshiibm wants to merge 1 commit into
anaghajoshiibm wants to merge 1 commit into
Conversation
…teway Signed-off-by: Anagha Joshi <anagha.joshi3@ibm.com>
anaghajoshiibm
force-pushed
the
drs-feat
branch
from
August 14, 2026 09:32
ab9b195 to
51b9093
Compare
Collaborator
Author
|
Validation - 
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PR summary
Regenerated Transit Gateway Python SDK from updated spec to support the new dynamic_route_server connection type introduced by the DRS feature. Added integration test covering full CRUD lifecycle for the new connection type.
Fixes: IBM/networking-go-sdk#309
PR Checklist
Please make sure that your PR fulfills the following requirements:
PR Type
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change?