Fetch VNF package content manifest

Use this API to obtain package manifest contained in an on-boarded VNF package. The API consumer can use this resource to obtain the content of the manifest.

The following elements of the request, example, and responses are described:

Request

Table 1. Request
Aspect Value
Endpoint URL /api/etsi/vnfpkgm/v2/vnf_packages/<package-id>/manifest
HTTP Method GET

Request headers

Table 2. Request headers
Header Value
Version 2.1.0
Accept Must be set to application/zip or compatible (such as */*) when the include_signatures query parameter flag is specified.

Request data

None

Request data example

None

URI query parameters

Table 3. URI query parameters
Parameter name Description
include_signatures

This parameter is optional.

If this parameter is provided, the orchestration component returns the manifest and related security information (such as certificate) in a ZIP archive. If this parameter is not given, the NFVO provides only a copy of the manifest file. This URI query parameter is a flag; for example, it has no value.

Response codes

Table 4. Response codes
HTTP status code Description
200 The VNF Package manifest content has been successfully retrieved.
400 The response body contains details about the error.
404 When No Package for supplied ID is found.
406 If the related request contained an Accept header not compatible with the Content type application/zip but the include_signatures flag was provided.
409 Typically, this code is caused because the onboarding state of the VNF package has a value different from ONBOARDED.
500 Internal Server Error
4xx/5xx In addition to the response codes defined in this table, any common error response codes.

Response headers

Table 5. Request headers
Header Value
Content-Type text/plain or application/zip

Response data

If the include_signatures flag was provided, a successful response payload body contains the content of the package manifest file in plain text, or as a ZIP file with related security files, such as certificates.