some of the ETSI Catalog Manager error codes are too generic, for example, /api/catalog/v1/vnfpackges. We use this API for posting a new SDC. Please see the following test cases.

Currently, success status code is 200 for the request and error code is 0. 

Is it possible we have an error code for the “PACKAGE_ALREADY_EXISTS”? This would be a business error, not a system error. There are several other error issues, but we like to start from this.

 

Background:

If the package does already exist in the ETSI Catalog, the “status” of “error” is quite difficult to use for this scenario as it provides no information on what the actual problem is.  You can see below in the response that the “status” is simply “error” (where the statusDescription is more accurate), this doesn’t give us any information on what the problem is. Would it be possible to get the status for this scenario to show “package already exists” or something to that effect in order to handle this scenario gracefully? 

Current Response to Job Status Check:

 

{

  "jobId": "5fa51343-f754-4c63-af07-f6086451effc",

  "responseDescriptor": {

    "status": "error",

    "progress": "255",

    "statusDescription": "VNF package() already exists.",

    "errorCode": "0",

    "responseId": "2",

    "responseHistoryList": [

     

{         "status": "processing",         "progress": "5",         "statusDescription": "Start CSAR(d4086b15-98b7-4000-b24c-9119439e4cb4) distribute.",         "errorCode": "0",         "responseId": "1"       }

    ]

  }

}