Identify Vnet GUID for conflicting VNI #99
Merged
Conversation
This file contains 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
prsunny
approved these changes
Dec 9, 2021
|
please also update the description with previous output and new output |
sumukhatv
added a commit
that referenced
this pull request
Jul 27, 2022
sumukhatv
added a commit
that referenced
this pull request
Jul 27, 2022
abdosi
added a commit
to sonic-net/sonic-buildimage
that referenced
this pull request
Jul 29, 2022
commit 5f7cb77230fceb1b7fd30c57a70d0cd05cd6dd95 (HEAD -> 201911, origin/201911)
Author: Sumukha Tumkur Vani <sumukhatv@outlook.com>
Date: Wed Jul 27 16:51:38 2022 -0700
Use 201911/stretch dependencies for build (#118)
commit e3809523050df75ec18bf31a5dc3a2e595d58a14
Author: Sumukha Tumkur Vani <sumukhatv@outlook.com>
Date: Wed Jul 27 15:17:12 2022 -0700
Change response message for conflicting VNI (#117)
Ref: sonic-net/sonic-restapi#99
Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While creating a new VNET with the same VNI, the API caller might find it useful to know the exiting Vnet GUID for the conflicting VNI. Hence, we are modifying the VNET create API to return the Vnet GUID of the conflicting VNI
Existing response: "Object already exists: 1001"
New response: "Object already exists: {"vni": "1001", "vnet_name": "vnet_guid_1"}