Bugfix - CSAR packing for operations of same WF

Fix for failed CSAR packaging if user creates two
operations and associated workflows having artifacts
to them. Updated the operation name before artifact
name to make it unique before adding to zip

Change-Id: I1c1997199ba015a0ce2fc35cda9696031babaebe
Issue-ID: SDC-1802
Signed-off-by: ojasdubey <ojas.dubey@amdocs.com>

diff --git a/catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ArtifactsBusinessLogic.java b/catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ArtifactsBusinessLogic.java
index f104079..4ef2e06 100644 (file)
--- a/catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ArtifactsBusinessLogic.java
+++ b/catalog-be/src/main/java/org/openecomp/sdc/be/components/impl/ArtifactsBusinessLogic.java
@@ -3145,7 +3145,7 @@ public class ArtifactsBusinessLogic extends BaseBusinessLogic {
 
         Operation operation = optionalOperation.get();
         ArtifactDefinition implementationArtifact =  operation.getImplementationArtifact();
-        implementationArtifact.setArtifactName(artifactInfo.getArtifactName());
+        implementationArtifact.setArtifactName(operation.getName() + "_" + artifactInfo.getArtifactName());
         implementationArtifact.setDescription(artifactInfo.getDescription());
         implementationArtifact.setArtifactType(artifactInfo.getArtifactType());
         operation.setImplementation(implementationArtifact);