Puppet Community

which more or less sums up every experience I've had with nmcli

oh, it wants it prior to subcommands :facepalm:

oh boy, a strange custom format to parse instead of providing json, great choice

E.g.
```IP4.ROUTE[18]:dst = 198.32.252.208/31, nh = 10.229.140.134, mt = 408
IP4.ROUTE[19]:dst = 198.32.252.210/31, nh = 10.229.140.134, mt = 408```

if only systemd-networkd was part of BaseOS

I don't understand why it didn't make it into EL9

unless you feel like rolling your own libgrok could help <@U1QVBAUS2>

looks like it hasn't had an update in 4 years: <https://rubygems.org/gems/jls-grok>

This depends on jls-grok and has frequent updates <https://rubygems.org/gems/logstash-filter-grok>

<https://github.com/jordansissel/ruby-grok>

mmm sad. it is far nicer to build parsers in than raw regex.

it's not terribly complicated and it's relied on by logstash users a lot so it might just be you know.. mature software :wink:

it looks like ruby's dbus bindings are long dead too

I think maybe writing out the file and then shelling out to run nmcli to kick interfaces may be the least-worst option

<https://kellyjonbrazil.github.io/jc/docs/parsers/nmcli|https://kellyjonbrazil.github.io/jc/docs/parsers/nmcli>

I have no issue with epel packages.  Are you using networkd in production?

To date I only have used it under fedora for personal boxes.

Are you using systemd::network to configure entire files?

I considered writing a type/provider for it to reload the interface but didn't have a high need for it yet

I have per interfaces routes in hiera, which is definitely a nice to have.

Waaa?
```NetworkManager-initscripts-updown-1:1.36.0-7.el8_6.noarch : Legacy ifup/ifdown scripts for NetworkManager that replace initscripts (network-scripts)
Repo        : baseos
Matched from:
Filename    : /usr/sbin/ifup```

<@U1QVBAUS2> if you want to write a type/provider, maybe ping <@U11QGB2PN>, he mentioned it as well

My brain fails at comprehending exactly how this provider works and how to test it, annoying.

Yeah, the weird finicky stuff. Haven't quite understood the hoops yet how and when those receives come into play and whatnot

Literally just randomly shoving code around until it sticks isn't helping :smile:

Should probably open up the documentation and actually figure out how that works in detail

Because osmosis isn't working :neutral_face:

that's exactly how I feel every time I touch puppet providers :shrug:

Eh, the actual provider isn't the problem, but the whole rspec environment is still a bit of a "yeah, magic somewhere, just write patterns here and it works"