goSDN merge requestshttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests2022-03-30T08:21:53Zhttps://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/367Draft: Improve Security with more linting, govet2022-08-05T11:35:19ZGhost UserDraft: Improve Security with more linting, govet<!--- 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 #242https://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 #336https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/338Draft: Resolve "Database PND store is missing option to search by name"2022-12-15T12:09:32ZGhost UserDraft: Resolve "Database PND store is missing option to search by name"<!--- 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: -->
#223https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/403Draft: Resolve "Deal with read-only fields in YANG"2023-04-17T13:43:46ZMalte BauchDraft: Resolve "Deal with read-only fields in YANG"<!--- 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 #258https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/399Draft: Resolve "Implement our own version to send gNMI requests"2022-12-15T12:11:10ZFabian SeidlDraft: Resolve "Implement our own version to send gNMI requests"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
See #246<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
See #246https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/368Draft: Resolve "Improve security by enabling and enforcing more linting rules...2022-10-12T13:53:11ZGhost UserDraft: Resolve "Improve security by enabling and enforcing more linting rules, govet options"<!--- 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 #242https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/108Draft: Resolve "Refactoring of CLI-handling"2021-04-12T09:17:35ZGhost UserDraft: Resolve "Refactoring of CLI-handling"Closes #76Closes #76Martin StiemerlingMartin Stiemerlinghttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/790Draft: Resolve "Update gRPC abstraction API with missing calls and refactoring"2024-03-19T08:26:08ZFabian 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/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/450Resolve "After failing to add a network element to the storage, it is not pos...2023-04-17T09:38:43ZMalte BauchResolve "After failing to add a network element to the storage, it is not possible to redo this because of an issue with a file lock in the plugin regitry"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
This change fixes the `text file is busy` error if multiple network elements are registered using the same p...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
This change fixes the `text file is busy` error if multiple network elements are registered using the same plugin. With this change it is ensured that the `RequestPlugin` method within the controller checks if the requested plugin has already been requested before and is therefore already present. If this is the case the plugin is reused and not downloaded again. Plugin has been extended with the path to the executable that is used.
## 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: -->
#279
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
If multiple network elements are registered using the same plugin requested from the plugin registry the user was presented with the `text file is busy` error. It should be possible to create multiple devices using the same plugin.
## 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. -->
Multiple devices with the same plugin have been created and the corresponding database entries have been checked. If a plugin was already requested once it is not downloaded again.
## 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.
Closes #279https://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/400Resolve "Clean up deafult pnd uuid in toml files"2022-11-11T11:17:49ZFabian SeidlResolve "Clean up deafult pnd uuid in toml files"<!--- 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 #261https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/309Resolve "CLI can currently only be used in prompt mode because authorization ...2022-05-12T09:43:16ZMalte BauchResolve "CLI can currently only be used in prompt mode because authorization can not be set in the other mode"<!--- 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 #202https://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/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/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/369Resolve "Delete the store files after the unit testing"2022-08-17T15:26:06ZGhost UserResolve "Delete the store files after the unit testing"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
Fixed issue described in #221. Also fixed an additional issue with pnds and a toml file after running the wh...<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
Fixed issue described in #221. Also fixed an additional issue with pnds and a toml file after running the whole test suite.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/370Resolve "Error handling in event publishing via entity services could be impr...2022-10-14T11:13:13ZGhost UserResolve "Error handling in event publishing via entity services could be improved"<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
See #248<!--- Provide a general summary of your changes in the Title above -->
## Description
<!--- Describe your changes in detail -->
See #248