Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-2334

SDC Workflow Designer images are not following the SDC naming convention

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Low Low
    • Guilin Release
    • Dublin Release
    • I currently have commit aa3351b0197d96469dd1c34abd0489c09756eaa4 from gerrit.onap.org/r/sdc/sdc-workflow-designer, but this seems to apply to all versions looking at the actual images available in ONAP nexus.

      What

      The docker images produced by sdc-workflow-designer () do not have a sdc prefix as all other sdc images have. This is very confusing as many other ONAP components have a related or unrelated workflow concepts so this is not distinguishable. On practical level it makes searching, grepping and similar operations to focus on all sdc elements harder.

       

      For example in oom/kubernetes/sdc/charts/sdc-wfd-be/values.yaml has

      image: onap/workflow-backend:1.4.0
      configInitImage: onap/workflow-init:1.4.0

      in contrast to all other sdc charts (including the other plugin designed dcae-ds) have something like this: example from oom/kubernetes/sdc/charts/sdc-be/values.yaml

      image: onap/sdc-backend:1.4.0
      backendInitImage: onap/sdc-backend-init:1.4.0

       

      **This is of course not just an OOM thing but in poms etc.

       

      Expected Result

      **workflow designed image sto be tagged using the same naming convention as the rest of the sdc and most of the rest of ONAP

       

      Reproducible

      Yes, every time

            vasraz vasraz
            t.puha t.puha
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: