Joshua Powers

Hey @LukeWinikates, Looking through this code, I can see what you have a few questions as I am not entirely clear looking back at this as well :) To start,...

Thanks for taking a look at this and sharing your thoughts! > I've been thinking about what would be the safest, most considerate way to change the default behavior to...

Hi, There are some troubleshooting steps in the [plugin readme](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/wireguard#troubleshooting), specifically: 1) making sure that telegraf has the right capabilities 2) ensuring `wg show` shows the devices you think are...

> if CGO_ENABLED is set to 1, which is explicitly set to 0 in the Telegraf Makefile. I'm assuming that's there on purpose because of a known problem? This is...

Does the CLI have a JSON or other format option? We strongly dislike parsing CLI output due to changes, whitespace, etc., but if there is a parseable output, we are...

I am not opposed to an opt-in parsing option. I think the fact that the library we were using will not be able to be updated without work can further...

Sweet! We have some guidelines here: https://github.com/influxdata/telegraf/tree/master/docs/developers If you have more specific questions, you can ask them here (although I'm about to disappear for the rest of the year) or...

In general, if we cannot connect an output telegraf will not start. This is the expected behavior as it prevents scenarios where a user is using a wrong password or...

I am going to mark this upstream, as the client library we are currently using appears to require cgo for freebsd support. It does look like [openbsd](https://github.com/WireGuard/wgctrl-go/pull/54) does not require...

> Could you please also point me where did I fail with the semantic of PR? If your PR only contains a single commit, the semantic checker uses that to...