commit c73f78ef267ec0bb4552cdaf74f0a42e8078e2ee
author Chenfei Gao <cgao@research.att.com> Thu Jan 09 13:33:12 2020 -0500
committer Chenfei Gao <cgao@research.att.com> Mon Jan 13 12:32:40 2020 -0500
tree 3ab1be8a1fb3dd19154090291e17eb6b691f19c7
parent 1d801e7c49105b19ac7bfd3f7addbac995fd1dc8

Added the new versioning validation for policy and policy type

The following rules are implemented to validate the version provided
in the POST payloads of policies and policy types:

1) If version field is not specified in POST payload, "406 - Not Acceptable"
   would be returned along with the message "mandantory version field is missing".
2) If the version is not in the DB, we simply insert it.
3) If the version is in the DB, "406 - Not Acceptable" is returned along with
   the message saying "specified version x.x.x" is already existing and the latest
   version is x.x.x. It can force the user to create a newer version than the latest one.
4) The same versioning validation is applied to legacy types of policies too
   so that everything is consistent.

Issue-ID: POLICY-2316
Change-Id: I395df0196a9d3073fd1f09060f943aeeb554d277
Signed-off-by: Chenfei Gao <cgao@research.att.com>