feat: (EVPN GW API) Add "components" field to each API object's status #445
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
This is an API enhancement for the EVPN GW use case. The addition of a "components" field in the status sector of each API object will enable the capture of the state and details that are generated by the different subscribed components (FRR component, Linux component, etc...) which are realizing the configuration for each API object. Signed-off-by: Dimitrios Markou <dimitrios.markou@ericsson.com>
sandersms
approved these changes
Mar 4, 2024
|
Thank you @sandersms |
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.
This is an API enhancement for the EVPN GW use case.
The addition of a "components" field in the status sector of each API object will enable the capture of the state and details that are generated by the different subscribed components (FRR component, Linux component, etc...) which are realizing the configuration for each API object.
This addition follows the re-architecture of the opi-evpn-br which has been described here