Make type and type_version mandatory on policies

Up until now, the "type" and "type_version" fields defaulted to "NULL"
and "0.0.0" respectively when they were not specified because the
"type_version" field was not always specified on policies in previous
releases. In cases where the "type_version" field was not specified, it
was assumend that a "0.0.0" version of the policy type existed. In
parallel, if the version field was not specified on the policy type, the
version was stored as 0.0.0.

This behaviour is now changed and the "type" and "type_version" fields
are now always mandatory.

Issue-ID: POLICY-2538
Change-Id: Ieec97f4a111edd13dbe31116c7549f07c19ef0aa
Signed-off-by: liamfallon <liam.fallon@est.tech>
2 files changed
tree: f74d5536f3bd8235b8d637c16ba5ce155a1e9fb0
  1. main/
  2. packages/
  3. releases/
  4. testsuites/
  5. .gitignore
  6. .gitreview
  7. INFO.yaml
  8. LICENSE.txt
  9. lombok.config
  10. pom.xml
  11. README.md
  12. version.properties
README.md

Copyright 2017-2018 AT&T Intellectual Property. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains the ONAP Policy API code.

To build it using Maven 3, run: mvn clean install