goSDN merge requestshttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests2024-03-29T00:06:08Zhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/815[renovate] Update renovate/renovate Docker tag to v37.274.02024-03-29T00:06:08Zrenovate_bot[renovate] Update renovate/renovate Docker tag to v37.274.0This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [renovate/renovate](https://renovatebot.com) ([source](https://github.com/renovatebot/renovate)) | image | minor | `37.273.0` -> `37.274.0`...This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [renovate/renovate](https://renovatebot.com) ([source](https://github.com/renovatebot/renovate)) | image | minor | `37.273.0` -> `37.274.0` |
> :exclamation: **Important**
>
> Release Notes retrieval for this MR were skipped because no github.com credentials were available.
> If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes).
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
â™» **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this MR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box
---
This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yNzMuMCIsInVwZGF0ZWRJblZlciI6IjM3LjI3My4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=-->https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/814[renovate] Update golangci/golangci-lint Docker tag to v1.57.22024-03-29T00:05:57Zrenovate_bot[renovate] Update golangci/golangci-lint Docker tag to v1.57.2This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [golangci/golangci-lint](https://github.com/golangci/golangci-lint) | image | patch | `v1.57.1-alpine` -> `v1.57.2-alpine` |
> :exclamatio...This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [golangci/golangci-lint](https://github.com/golangci/golangci-lint) | image | patch | `v1.57.1-alpine` -> `v1.57.2-alpine` |
> :exclamation: **Important**
>
> Release Notes retrieval for this MR were skipped because no github.com credentials were available.
> If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes).
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
â™» **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this MR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box
---
This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yNzMuMCIsInVwZGF0ZWRJblZlciI6IjM3LjI3My4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=-->https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/811Draft: update submodules2024-03-26T00:39:49ZNeil-Jocelyn ScharkDraft: update submodules<!--- 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.Neil-Jocelyn ScharkNeil-Jocelyn Scharkhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/806[renovate] Update module github.com/docker/docker to v262024-03-29T00:06:11Zrenovate_bot[renovate] Update module github.com/docker/docker to v26This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [github.com/docker/docker](https://github.com/docker/docker) | require | major | `v24.0.9+incompatible` -> `v26.0.0+incompatible` |
> :exc...This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [github.com/docker/docker](https://github.com/docker/docker) | require | major | `v24.0.9+incompatible` -> `v26.0.0+incompatible` |
> :exclamation: **Important**
>
> Release Notes retrieval for this MR were skipped because no github.com credentials were available.
> If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes).
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
â™» **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this MR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box
---
This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yNTYuMCIsInVwZGF0ZWRJblZlciI6IjM3LjI1Ni4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIn0=-->https://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/784Draft: Resolve "Integration test for Lab01"2024-03-06T14:22:57ZKatharina RenkDraft: Resolve "Integration test for Lab01"<!--- 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 #349Katharina RenkKatharina Renkhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/769Draft: Stateless plugins2024-03-01T16:35:03ZMalte BauchDraft: Stateless plugins<!--- 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.Malte BauchMalte Bauchhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/712Draft: Resolve "Lint shadowing of global variables"2024-03-06T13:28:47ZNeil-Jocelyn ScharkDraft: Resolve "Lint shadowing of global variables"<!--- 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 #351Neil-Jocelyn ScharkNeil-Jocelyn Scharkhttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/701Draft: Resolve "Applying a SDN configuration should also update the internal ...2024-01-16T16:35:37ZMalte BauchDraft: Resolve "Applying a SDN configuration should also update the internal configuration of managed 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 #350https://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/589Draft: Test devcontainer rosetta2023-10-30T10:33:48ZNeil-Jocelyn ScharkDraft: Test devcontainer rosetta<!--- 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.https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/557Draft: Refactor nucleus to remove hard dependencies on structs2023-10-09T06:11:41ZAndre SterbaDraft: Refactor nucleus to remove hard dependencies on structs## Description
The idea is to add an aditional layer around the `core models` (like networkElement and others).
This will enable more flexibility in the `nucleus` package and remove problems with circular dependencies and the question ...## Description
The idea is to add an aditional layer around the `core models` (like networkElement and others).
This will enable more flexibility in the `nucleus` package and remove problems with circular dependencies and the question `where to place interfaces for our services, stores, ...?`.
This should also remove the `interfaces` folder that is filled with interfaces and structs.
After this we can also think about moving movings like `rbac` and `topology` back in the nucleus instead of in own packages and shared functionalitiy (like stores and services).
This will roughly follow the ideas of ports&adapters, hexagonal architecture and/or onion architecture. (I like this [article](https://www.happycoders.eu/de/software-craftsmanship/hexagonale-architektur/) about it)
## Related Issue
## Motivation and Context
## How Has This Been Tested?
## Screenshots (if appropriate):
## Types of changes
* [ ] 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:
* [ ] 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/548Draft: Resolve "Deadline and Cancellation for gRPC calls"2023-09-11T16:35:15ZMalte BauchDraft: Resolve "Deadline and Cancellation for gRPC calls"<!--- 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 #320https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/535Draft: Extend the MR template, note that a general summary is now mandatory2023-09-01T10:42:26ZMalte BauchDraft: Extend the MR template, note that a general summary is now mandatory<!--- Provide a general summary of your changes in the Title above -->
The merge request template has been extended. From now on a general summary for a MR is mandatory.
## Description
<!--- Describe your changes in detail -->
Creating ...<!--- Provide a general summary of your changes in the Title above -->
The merge request template has been extended. From now on a general summary for a MR is mandatory.
## Description
<!--- Describe your changes in detail -->
Creating a new merge request with the help of the default template will now inform the user that it is mandatory to provide a general summary.
From now on merge request without one will not be merged anymore (this applies for everyone, no excuses).
In general it is preferred that all the sections in the template are addressed but we expect at least a **proper** general summary from now on.
## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
Most of our merge requests do not provide proper explanation about the changes and their purpose. Providing a general summary makes it easier to understand the context of a MR and it will also help us in the future to list all the changes in a new release.https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/534[renovate] Update module github.com/hashicorp/go-plugin to v1.6.02024-03-29T00:06:02ZGhost User[renovate] Update module github.com/hashicorp/go-plugin to v1.6.0This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [github.com/hashicorp/go-plugin](https://github.com/hashicorp/go-plugin) | require | minor | `v1.4.10` -> `v1.6.0` |
---
> âš **Warning**
...This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [github.com/hashicorp/go-plugin](https://github.com/hashicorp/go-plugin) | require | minor | `v1.4.10` -> `v1.6.0` |
---
> âš **Warning**
>
> Some dependencies could not be looked up. Check the warning logs for more information.
> :exclamation: **Important**
>
> Release Notes retrieval for this MR were skipped because no github.com credentials were available.
> If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes).
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
â™» **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this MR and you won't be reminded about this update again.
---
- [x] <!-- rebase-check -->If you want to rebase/retry this MR, check this box
---
This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi42Ny4xIiwidXBkYXRlZEluVmVyIjoiMzcuNjUuMSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciJ9-->https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/488Draft: Psd vgu logging2023-07-14T06:45:03ZAdrian BusseDraft: Psd vgu loggingVGU PSD
## Description
merge two sites of the loggingVGU PSD
## Description
merge two sites of the logginghttps://code.fbi.h-da.de/danet/gosdn/-/merge_requests/484Draft: Resolve "Related/Existing work about change logic for yang models"2023-08-03T12:19:59ZMalte BauchDraft: Resolve "Related/Existing work about change logic for yang models"<!--- 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.
See #296, #290, #287, #152, #113, #255https://code.fbi.h-da.de/danet/gosdn/-/merge_requests/374Draft: Deployment docker compose2023-01-19T13:25:41ZGhost UserDraft: Deployment docker compose<!--- 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.