Uploaded image for project: 'Data Collection, Analytics, and Events'
  1. Data Collection, Analytics, and Events
  2. DCAEGEN2-2140

escaped string in spec file not included on the blueprint generated.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Medium Medium
    • Guilin Release
    • Frankfurt Release
    • None

      VESCollector has below attribute on spec file

        { "name": "collector.schema.file", "value": "{\"v1\":\"./etc/CommonEventFormat_27.2.json\",\"v2\":\"./etc/CommonEventFormat_27.2.json\",\"v3\":\"./etc/CommonEventFormat_27.2.json\",\"v4\":\"./etc/CommonEventFormat_27.2.json\",\"v5\":\"./etc/CommonEventFormat_28.4.1.json\",\"v7\":\"./etc/CommonEventFormat_30.1.1.json\"}", "description": "VES schema file name per version used for validation", "designer_editable": true, "sourced_at_deployment": false, "policy_editable": false },
       
      The o/p blueprint generated removes the escaping.
       
         collector.schema.file: '{"v1":"./etc/CommonEventFormat_27.2.json","v2":"./etc/CommonEventFormat_27.2.json","v3":"./etc/CommonEventFormat_27.2.json","v4":"./etc/CommonEventFormat_27.2.json","v5":"./etc/CommonEventFormat_28.4.1.json","v7":"./etc/CommonEventFormat_30.1.1.json"}'     
       

        1. ONAP_vesK8sWithoutd_Jira2140.yaml
          6 kB
        2. ves_Jira2140.json
          9 kB

            vv770d vv770d
            vv770d vv770d
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: