-
Bug
-
Resolution: Done
-
Medium
-
Istanbul Release
-
None
The import file generated when a new type is added into the system, additional_type_definitions.yaml, is missing types entries (i.e. 'data_types:', 'policy_types:') and header. Also, the solution is not considering the types entries, i.e. 'data_types:', 'policy_types:', etc., when replacing types and generating the new file, which renders the solution broken.
Example of current file being generated:
tosca.datatypes.nfv.ServiceAvailability: derived_from: tosca.datatypes.Root description: additional type tosca.datatypes.nfv.L2AddressData: derived_from: tosca.datatypes.Root description: additional type tosca.datatypes.nfv.Unknown: derived_from: tosca.datatypes.Root description: additional type
How the file should be generated:
tosca_definitions_version: tosca_simple_yaml_1_3
description: Auto-generated file that contains package custom types or types added after system installation.
data_types:
tosca.datatypes.nfv.ServiceAvailability:
derived_from: tosca.datatypes.Root
description: additional type
tosca.datatypes.nfv.L2AddressData:
derived_from: tosca.datatypes.Root
description: additional type
tosca.datatypes.nfv.Unknown:
derived_from: tosca.datatypes.Root
description: additional type