diff options
Diffstat (limited to 'src/onapsdk')
| -rw-r--r-- | src/onapsdk/cds/data_dictionary.py | 21 | ||||
| -rw-r--r-- | src/onapsdk/sdc/service.py | 4 | ||||
| -rw-r--r-- | src/onapsdk/sdc/vf.py | 2 |
3 files changed, 15 insertions, 12 deletions
diff --git a/src/onapsdk/cds/data_dictionary.py b/src/onapsdk/cds/data_dictionary.py index b4d8d0e..27cfc29 100644 --- a/src/onapsdk/cds/data_dictionary.py +++ b/src/onapsdk/cds/data_dictionary.py @@ -136,6 +136,7 @@ class DataDictionary(CdsElement): - "entry_schema" - "updatedBy" - "definition" + "definition" key value should contains the "raw" data dictionary. Returns: @@ -153,15 +154,17 @@ class DataDictionary(CdsElement): this kind of data dictionary can't be uploaded to blueprintprocessor. That method tries to fix it. It can be done only if "raw" data dictionary has a given schema: - { - "name": "string", - "tags": "string", - "updated-by": "string", - "property": { - "description": "string", - "type": "string" - } - } + + .. code-block: json: + { + "name": "string", + "tags": "string", + "updated-by": "string", + "property": { + "description": "string", + "type": "string" + } + } Raises: ValidationError: Data dictionary doesn't have all required keys diff --git a/src/onapsdk/sdc/service.py b/src/onapsdk/sdc/service.py index 44a26e8..507b068 100644 --- a/src/onapsdk/sdc/service.py +++ b/src/onapsdk/sdc/service.py @@ -406,8 +406,8 @@ class Service(SdcResource): # pylint: disable=too-many-instance-attributes, too Load VNFs from components generator. It creates a generator of the vf modules as well, but without - vf modules which has "vf_module_label" property value equal - to "base_template_dummy_ignore". + vf modules which has "vf_module_label" property value equal + to "base_template_dummy_ignore". Returns: Iterator[Vnf]: Vnf objects iterator diff --git a/src/onapsdk/sdc/vf.py b/src/onapsdk/sdc/vf.py index 7e4e4a7..3b979b5 100644 --- a/src/onapsdk/sdc/vf.py +++ b/src/onapsdk/sdc/vf.py @@ -72,7 +72,7 @@ class Vf(SdcResource): If Vf is created vendor is get from it's resource metadata. Otherwise it's vendor provided by the user or the vendor from vsp. It's possible that method returns None, but it won't be possible then - to create that Vf resource. + to create that Vf resource. Returns: Optional[Vendor]: Vendor object related with Vf |