From 796bfad22dae30e39f678c38fc9fba4f7f96032b Mon Sep 17 00:00:00 2001 From: Monty Taylor Date: Sat, 6 Jun 2015 09:40:03 -0400 Subject: Use json for in-tree cloud data In preparation for sharing the default and vendor data with other projects, potentially even non-python ones, move the data into json format, which is slighly less exciting to read, but has more widespread standard library support. The user-facing config file will still be in yaml format, because that's easier on the eyes and it's expected to be read and edited by humans. Continue to accept yaml everywhere, because an end user may have dropped a yaml config file into a dir somewhere, and that's fine. Change-Id: I269d31e61da433ac20abb39acdde0f9f9fe12837 --- test-requirements.txt | 1 + 1 file changed, 1 insertion(+) (limited to 'test-requirements.txt') diff --git a/test-requirements.txt b/test-requirements.txt index 62f3e88..9a02b04 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -8,6 +8,7 @@ coverage>=3.6 extras fixtures>=0.3.14 discover +jsonschema>=2.0.0,<3.0.0,!=2.5.0 python-keystoneclient>=1.1.0 python-subunit>=0.0.18 sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3 -- cgit v1.2.1