Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Barry Scott <barry@barrys-emacs.org>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] wg show: Add json output
Date: Mon, 24 Feb 2020 19:28:07 +0000	[thread overview]
Message-ID: <219C0F7A-E7F7-46BD-9E38-09D620299053@barrys-emacs.org> (raw)
In-Reply-To: <6631a080206c608c7b92cffab3f739c66a1ff1e8.camel@gmail.com>



> On 23 Feb 2020, at 12:45, Arti Zirk <arti.zirk@gmail.com> wrote:
> 
> On E, 2020-02-17 at 15:47 +1100, Matthew Oliver wrote:
>> Someone asked about this in the IRC channel, so quickly wrote up a
>> patch to add it. No pressure if you do/don't want to merge it :)
> 
> If you have wireguard-tools package installed then it should be
> possible to use the incldued wg-json script to do the same
> 
>  sudo /usr/share/wireguard-tools/examples/json/wg-json

When I built my tools in python on top of the wg command I was
please to see a machine interface, but find the \t separated list
of values odd to find in a modern app.

I think it would be a good addition to have the JSON output
without the need to use a contrib script. Many text commands
output in JSON or XML for ease of interfacing.

The JSON would also provide a nice way to add more attributes
in the future.

Barry

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2020-02-25  0:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  3:57 Matthew Oliver
2020-02-17  4:47 ` Matthew Oliver
2020-02-23 11:00   ` Jason A. Donenfeld
2020-02-25 15:49     ` Julian Orth
2020-02-23 12:45   ` Arti Zirk
2020-02-24 19:28     ` Barry Scott [this message]
2020-02-25 14:50       ` Kalin KOZHUHAROV

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=219C0F7A-E7F7-46BD-9E38-09D620299053@barrys-emacs.org \
    --to=barry@barrys-emacs.org \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).