goSDN merge requestshttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests2024-03-28T09:43:42Zhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/790Draft: Resolve "Update gRPC abstraction API with missing calls and refactoring"2024-03-28T09:43:42ZFabian SeidlDraft: Resolve "Update gRPC abstraction API with missing calls and refactoring"## Description
Complete:
- [x] User
- [x] Role
- [ ] Pnd
* To dicuss: CreatePnd call, uses CreatePndList, should name of the API call be the same even if we only gice the option to add one? Can we make it optional to add multiple in ...## Description
Complete:
- [x] User
- [x] Role
- [ ] Pnd
* To dicuss: CreatePnd call, uses CreatePndList, should name of the API call be the same even if we only gice the option to add one? Can we make it optional to add multiple in the API call too?
* Maybe do only one call where a list of one or many is provided?
- [ ] Plugin
* Maybe move GetPluginSchemaTree from MNE to Plugin?
- [ ] MNE
* For creation: Maybe do only one call where a list of one or many is provided?
* Need to discuss Update function again!
- [x] Auth
Missing for now. Maybe implement?:
- [x] ConfigurationManagement
- [ ] Route (Not implemented because this will probably get reworked)
- [ ] Topology (Not implemented because this will probably get reworked)
- [x] App
Related to #359https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/633Draft: Resolve "Add error handling for MNE watching if the provided paths do ...2023-11-30T08:49:37ZFabian SeidlDraft: Resolve "Add error handling for MNE watching if the provided paths do not exist"<!--- 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 #336