goSDN merge requestshttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests2021-04-15T11:16:11Zhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/143Investigate Security Issues2021-04-15T11:16:11ZGhost UserInvestigate Security Issues<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
#104 #105 #106 #107 #108 #109 #110
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
This merge request resolves a couple of security issues.
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
Using the established CI/CD testing pipeline.
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [x] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Closes #104
Closes #105
Closes #106
Closes #107
Closes #108
Closes #109
Closes #110v0.1.0 Codename Threadbarehttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/120Resolve "Code Quality"2021-03-26T20:36:36ZGhost UserResolve "Code Quality"Closes #85Closes #85v0.1.0 Codename Threadbarehttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/755Resolve "Credentials returned after registering an app are hard coded, which ...2024-02-19T09:44:02ZFabian SeidlResolve "Credentials returned after registering an app are hard coded, which causes problems if RabbitMQ is not hosted on localhost"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Related to #356https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/454Resolve "Change how gNMI paths are requested via NBI and controller"2023-05-23T14:48:39ZFabian SeidlResolve "Change how gNMI paths are requested via NBI and controller"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
See #280.
Also added updates to buf, because they were somehow forgotten the last time we wanted to.
CLI s...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
See #280.
Also added updates to buf, because they were somehow forgotten the last time we wanted to.
CLI shouldn't block for any paths for now, the fix is supposed to be temporary. Needs some further investigations in the future.https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/189Resolve "Deploy develop to Containerlab"2021-07-13T10:52:31ZMaximilian ReinheimerResolve "Deploy develop to Containerlab"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Closes #133SORTMaximilian ReinheimerMaximilian Reinheimerhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/92Resolve "Increase test coverage"2021-01-15T13:24:52ZGhost UserResolve "Increase test coverage"Closes #43Closes #43v0.1.0 Codename Threadbarehttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/540Resolve "PostRun function in cli does not get called if an error is thrown"2023-09-06T09:06:21ZMalte BauchResolve "PostRun function in cli does not get called if an error is thrown"<!--- Provide a general summary of your changes in the Title above -->
Update all CLI commands to use `Run` (no error returning) instead of `RunE` (run with returning errors), since we already had an error logging through `pterm`. Prompt...<!--- Provide a general summary of your changes in the Title above -->
Update all CLI commands to use `Run` (no error returning) instead of `RunE` (run with returning errors), since we already had an error logging through `pterm`. Prompt mode does check now for suggestions if the last cached suggestion is the right one for the current command.
## Description
<!--- Describe your changes in detail -->
For the prompt mode it is necessary to reset some variables if a command is executed. For this use case cobras `PostRun` function is used. But this function does not get called if the commands `RunE` function returns an error. Since we already inform the user through `pterm` about errors in the CLI it is possible to switch to the `Run` function.
This MR also addresses another bug within the prompt mode of the CLI. Copy pasting, or failed commands withing the CLI could result in wrong suggestions provided. This was caused through improper resetting of the suggestion cache. This has been fixed with this MR aswell.
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
Related to #309
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
Improves the overall usage of the CLI, since in a lot of cases a restart of the CLI was required.
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
If tested the most common sources of error, like e.g.:
- copy pasting of CLI commands
- using CTRL-C
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/405Resolve "To improve the device watching mechanism a fetch all after time inte...2022-12-22T11:16:26ZFabian SeidlResolve "To improve the device watching mechanism a fetch all after time interval method should be implemented"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
Implemented something different, than in #259 because the plan how we want to improve this changed. This sh...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
Implemented something different, than in #259 because the plan how we want to improve this changed. This should be also working with the planned upcoming changes to getting paths, adding mne, etc.https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/270178 Progress on authz, not properly implemented yet2022-03-30T08:21:53ZGhost User178 Progress on authz, not properly implemented yet<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
See #178 for changes and information about them.
Closes #178https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/265Resolve "Update NB API for user managment"2022-03-28T09:05:22ZGhost UserResolve "Update NB API for user managment"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
API updated with dummy requests for user management and implemented dummy interceptor for future authenticat...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
API updated with dummy requests for user management and implemented dummy interceptor for future authentication/authorization.
Implemented dummy requests for login and logout in cli.
Further steps / functions will be implemented in #178 & #179.
Closes #177https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/576Resolve "The key for more complex paths in the map containing information of ...2023-10-19T10:07:33ZMalte BauchResolve "The key for more complex paths in the map containing information of update events should be improved"<!--- Provide a general summary of your changes in the Title above -->
This MR changes the key for more complex paths (used within a subscribe event) from: `qkd_node/qkd_links/qkd_link" key:{key:"qkdl_id" value:"acde2729-3544-41c3-88cb-9...<!--- Provide a general summary of your changes in the Title above -->
This MR changes the key for more complex paths (used within a subscribe event) from: `qkd_node/qkd_links/qkd_link" key:{key:"qkdl_id" value:"acde2729-3544-41c3-88cb-9a9b82efeff0"/qkdl_status/` to `/qkd_link[qkdl_id=acde2729-3544-41c3-88cb-9a9b82efeff0]/qkdl_status`
## Description
<!--- Describe your changes in detail -->
Using ygot.PathToString instead of our current own method for path to string parsing, results in a more manageable key within the event's `pathAndValues` map
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
#326
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/568Resolve "Improve the event system by adding an extra Event for gNMI-Subscribe...2023-10-17T08:48:42ZFabian SeidlResolve "Improve the event system by adding an extra Event for gNMI-Subscribe to replace the currently used Update Event"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Related to #327https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/536Resolve "Exiting gosdnc causes the input in cli to be invisble"2023-09-05T10:08:33ZFabian SeidlResolve "Exiting gosdnc causes the input in cli to be invisble"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Related to #317Katharina RenkMalte BauchFabian Emil EnglertKatharina Renkhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/530Resolve "Investigate if TransportOption and Transport are both required when ...2023-08-30T11:40:46ZFabian SeidlResolve "Investigate if TransportOption and Transport are both required when creating network elements"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Related to #310Fabian SeidlFabian Seidlhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/523Resolve "Investigate MarshalJSON for network element in nucleus/networkelemen...2023-08-25T10:49:35ZFabian SeidlResolve "Investigate MarshalJSON for network element in nucleus/networkelement uses bson annotation for model"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Related to #312https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/516Resolve "Remove CSBI stuff from gosdnc"2023-09-01T12:15:35ZFabian SeidlResolve "Remove CSBI stuff from gosdnc"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Related to #311https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/513Resolve "Controller/Makefile uses older versions than the one in the top level"2023-08-21T07:55:44ZFabian SeidlResolve "Controller/Makefile uses older versions than the one in the top level"## Description
This also includes changes to the Makefile structure for cleaning purposes. Calls on the functions should work like they used to.
Related to #308## Description
This also includes changes to the Makefile structure for cleaning purposes. Calls on the functions should work like they used to.
Related to #308https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/508Resolve "Implement TLS support for SBI"2023-08-18T10:40:04ZFabian SeidlResolve "Implement TLS support for SBI"## Description
See #266## Description
See #266https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/504Resolve "Some of the example config files contain old or unusable values"2023-08-09T14:55:52ZFabian SeidlResolve "Some of the example config files contain old or unusable values"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
See #297<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
See #297https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/502Resolve "Update the way of building gnmi target container in Makefile"2023-08-10T10:30:57ZMalte BauchResolve "Update the way of building gnmi target container in Makefile"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggest...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
## Related Issue
<!--- This project only accepts merge requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
## Screenshots (if appropriate):
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
Closes #304