From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: Eric Garver <e@erig.me>,
netfilter-devel@vger.kernel.org,
Jones Desougi <jones.desougi+netfilter@gmail.com>
Subject: Re: [nft PATCH v2 0/2] JSON schema for nftables.py
Date: Wed, 22 May 2019 10:48:43 +0200 [thread overview]
Message-ID: <20190522084843.d5lx7223gi2pfiul@salvia> (raw)
In-Reply-To: <20190517201758.1576-1-phil@nwl.cc>
On Fri, May 17, 2019 at 10:17:56PM +0200, Phil Sutter wrote:
> This is basically identical to the RFC sent earlier. The only change is
> in second patch: As suggested by Eric, 'traceback' module is standard so
> there's no need to import it conditionally.
>
> The schema is still in its minimalistic form, I decided to extend it in
> follow-up patches.
I'm fine with this JSON validation, if no objections I'll push this
out.
Only one thing: I think it would be good if -s checks for -j in
nft-test.py, but not a deal breaker: this can be done in a follow up
patch.
Thanks.
> Changes since v1:
> - Fix patch 2 commit message, thanks to Jones Desougi who reported the
> inconsistency.
>
> Phil Sutter (2):
> py: Implement JSON validation in nftables module
> tests/py: Support JSON validation
>
> py/Makefile.am | 2 +-
> py/nftables.py | 30 ++++++++++++++++++++++++++++++
> py/schema.json | 17 +++++++++++++++++
> py/setup.py | 1 +
> tests/py/nft-test.py | 21 ++++++++++++++++++++-
> 5 files changed, 69 insertions(+), 2 deletions(-)
> create mode 100644 py/schema.json
>
> --
> 2.21.0
>
prev parent reply other threads:[~2019-05-22 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 20:17 [nft PATCH v2 0/2] JSON schema for nftables.py Phil Sutter
2019-05-17 20:17 ` [nft PATCH v2 1/2] py: Implement JSON validation in nftables module Phil Sutter
2019-05-22 13:03 ` Eric Garver
2019-05-17 20:17 ` [nft PATCH v2 2/2] tests/py: Support JSON validation Phil Sutter
2019-05-22 8:48 ` Pablo Neira Ayuso [this message]
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=20190522084843.d5lx7223gi2pfiul@salvia \
--to=pablo@netfilter.org \
--cc=e@erig.me \
--cc=jones.desougi+netfilter@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).