add possibility to manage network interfaces with a template #497
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trefzer
force-pushed
the
dev_network
branch
2 times, most recently
from
979abd5 to
16dd60c
Compare
kenyon
reviewed
Nov 12, 2024
kenyon
reviewed
Nov 13, 2024
Co-authored-by: Kenyon Ralph <[email protected]>
Co-authored-by: Kenyon Ralph <[email protected]>
Co-authored-by: Kenyon Ralph <[email protected]>
Co-authored-by: Kenyon Ralph <[email protected]>
traylenator
reviewed
Jan 19, 2025
bastelfreak
reviewed
Jan 19, 2025
traylenator
reviewed
Jan 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This gives the possibility to manage all network/netdev/link settings from hashes.
I'm aware of pull request #340 from @rwaffen which started an equal solution last year.
Since the development there does not seem to go on, I started this solution which currrently
gives us the opportunitiy to create any configuration stated in the systemd documentation.
All type defintions are taken out of systemd documentation (not documented, not in our type defintion).
I'm aware, that some types could defined more accurate, but I tried to get a compromise inbetween accurate type and
workload ;).