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: I4279adfa86f531205879dbb87986453604624032
Signed-off-by: liamfallon <liam.fallon@est.tech>
3 files changed
tree: 9ae867bf0ed606ab0cb791eb266be5fa120856d4
  1. models-base/
  2. models-dao/
  3. models-decisions/
  4. models-errors/
  5. models-examples/
  6. models-interactions/
  7. models-pap/
  8. models-pdp/
  9. models-provider/
  10. models-sim/
  11. models-tosca/
  12. releases/
  13. .gitignore
  14. .gitreview
  15. INFO.yaml
  16. LICENSE.txt
  17. lombok.config
  18. pom.xml
  19. README.md
  20. version.properties
README.md

Copyright 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 Model code that is agnostic to any PDP. It is common amongst all the repositories.

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