diff options
| author |   liamfallon <liam.fallon@est.tech> | 2019-05-07 12:42:26 +0000 |
|---|---|---|
| committer | liamfallon <liam.fallon@est.tech> | 2019-05-07 12:42:26 +0000 |
| commit | f53879588a464c727ece62f87c7625b47e6de7f1 (patch) | |
| tree | 980cddab937c38610587b50cc45a9c36540a2470 /models-examples/src/main/resources/policies/vDNS.policy.operational.input.json | |
| parent | e936413c9082afed0fef4646b8f12d351c87800c (diff) | |
Set default and check existance of Policy Type
The TOSCA specification has a "bug" in that it does not have a field to specify
the version of a policy type to use. We already had introduced the "type_version" field
for this.
This review introduces setting of the default version of a policy type to be
be used by a policy as the latest version of the policy type in the database.
As a side effect of this, we now have to check for existence of the policy type
of a policy in the database. This means that creation/update of a policy with
a non-existant policy type specified will now fail.
Issue-ID: POLICY-1738
Change-Id: I27080cf6cd358948810dab6897c72dfe4d41fe91
Signed-off-by: liamfallon <liam.fallon@est.tech>
Diffstat (limited to 'models-examples/src/main/resources/policies/vDNS.policy.operational.input.json')
0 files changed, 0 insertions, 0 deletions