Table of Contents
...
GAB is prepared as an independent library used for simple searching inside the yaml-file content. SDC exposes dedicated endpoint providing GABs base functionality over ONAP internal artifacts-data. Below you can find screenshot from the SDC swagger page, prepared to check documentation of describing the SDC endpoint for searching for a json paths inside the yaml file
...
ParentId and artifactUniqueId properties are needed to download artifact data from the Cassandra DAO. Content of the artifact is scanned for wanted fields and parsed to JSON response , - friendly for UI representations:
| Code Block |
|---|
{
"data": [{
"path1": "value1",
"path2": "value2"
},
{
"path1": "value3",
"path2": "value4"
}
]
} |
SDC FE integration
SDC's VF screen of Deployment Artifacts is extended to show also a button in shape of magnifier icon. Currently magnifier-button should be available for limited kinds of artifacts (at the moment only VES_EVENTS is supported), but there are also plans to handle other types of artifacts in next releases.
On a magnifier-button click, a dialog with populated data should appear. It is important to know that even GAB back-end services provides possibility to ask for whatever-fields with only one restriction about correct format (json paths) - for Dublin release only few predefined columns are considered to be shown by the GUI dialog: event.action[2], event.comment and event.faultFields.alarmAdditionalInformation.keyValuePair[ structure.key.value==faultId].comment.