add manage_network to manage networks in code

[rwaffen]

add manage_network so that one can define networks in code like one can do it with unit_files and manage_unit.

missing:

• maybe more complex types to check the *_entry in manage_network like in manage_unit.
• assert_Type does somehow not work in my local tests (Says its expecting a Resource Statement but got String)

early tests with code like this seem to work

include systemd

systemd::manage_network { 'myhome.network':
  match_entry   => {
    'Name' => 'enp0s8',
  },
  network_entry => {
    'Address' => '10.1.1.1/24',
    'Gateway' => '10.1.1.1',
  },
  address_entry => {
    'Address' => '10.1.1.2',
  },
}

[traylenator]

Appreciate it is WIP still.

[traylenator]

The rest of module uses present and absent . The fact it a file is a hidden detail.

[traylenator]

Rather than a new template the existing unit.epp could be extended to just support [Match], [Network] and [Address].

You would get manage_unit and manage_dropin of a network for free in the process. manage_unit .
manage_unit.

[rwaffen]

but wouldn't it get to overloaded, with dropin, units and networks? the initial 3 *_entry are only a subset, netword offers a lot more. so i thought better have it separated. otherwise you will never get a PR done if you have to check alle the influence you change could have?

[traylenator]

Easier to deal with the interaction in a common layer.

Template does need refactoring to loop over the section rather than enumerate them but that just strengthens case for one template.

[rwaffen]

¯_(ツ)_/¯ i also can add my stuff there, if this is whats needed to merge this in the end. i'm personally just not a big fand off such über-templates.

[trefzer]

@rwaffen are you still working on this ?