Commit cbd289bb authored by ETSI CTI's avatar ETSI CTI

Merge branch '2.7.1-dev' into 'master'

SOL005 OpenAPI representations for v2.7.1

See merge request !14
parents 0d258f2b 8886f39a
Pipeline #3231 passed with stage
in 0 seconds
# NFV SOL005 APIs
This repository hosts the [OpenAPI](https://www.openapis.org/) specificatons and other documentation
for the APIs defined in ETSI NFV GSs [SOL005](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/02.06.01_60/gs_NFV-SOL005v020601p.pdf).
for the APIs defined in ETSI NFV GSs [SOL005](https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/02.07.01_60/gs_NFV-SOL005v020701p.pdf).
The APIs described in this repository are defined for the `Os-Ma-nfvo` reference point.
......
swagger: "2.0"
info:
version: "1.1.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "1.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
title: "SOL005 - API version interface"
description: >
SOL005 - API version Interface
......@@ -17,8 +17,8 @@ info:
name: "NFV-SOL WG"
externalDocs:
description: ETSI GS NFV-SOL 005 V2.5.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/02.05.01_60/gs_NFV-SOL005v020501p.pdf
description: ETSI GS NFV-SOL 005 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/02.07.01_60/gs_NFV-SOL005v020701p.pdf
schemes:
- http
......@@ -34,17 +34,17 @@ paths:
###############################################################################
# API Versions #
###############################################################################
'/nsd/api-versions':
'/nsd/api_versions':
$ref: '../endpoints/SOL005_endpoints.yaml#/endpoints/api-versions'
'/nsfm/api-versions':
'/nsfm/api_versions':
$ref: '../endpoints/SOL005_endpoints.yaml#/endpoints/api-versions'
'/nslcm/api-versions':
'/nslcm/api_versions':
$ref: '../endpoints/SOL005_endpoints.yaml#/endpoints/api-versions'
'/nspm/api-versions':
'/nspm/api_versions':
$ref: '../endpoints/SOL005_endpoints.yaml#/endpoints/api-versions'
'/vnfpkgm/api-versions':
'/vnfpkgm/api_versions':
$ref: '../endpoints/SOL005_endpoints.yaml#/endpoints/api-versions'
\ No newline at end of file
swagger: "2.0"
info:
version: "1.1.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
version: "2.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1"
title: "SOL005 - NSD Management Interface"
description: >
SOL005 - NSD Management Interface
......@@ -17,10 +17,10 @@ info:
name: "NFV-SOL WG"
externalDocs:
description: ETSI GS NFV-SOL 005 V2.6.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/02.06.01_60/gs_NFV-SOL005v020601p.pdf
description: ETSI GS NFV-SOL 005 V2.7.1
url: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/005/02.07.01_60/gs_NFV-SOL005v020701p.pdf
basePath: /nsd/v1
basePath: /nsd/v2
schemes:
- http
......@@ -36,7 +36,7 @@ paths:
###############################################################################
# API Versions #
###############################################################################
'/api-versions':
'/api_versions':
$ref: '../endpoints/SOL005_endpoints.yaml#/endpoints/api-versions'
###############################################################################
......@@ -90,14 +90,12 @@ paths:
description: >
201 CREATED
An NS descriptor resource has been created
successfully, as a new NS descriptor resource.
The response body shall contain a representation
of the new NS descriptor resource, as defined in
clause 5.5.2.2.
The HTTP response shall include a "Location"
HTTP header that contains the resource URI of the
new NS descriptor resource.
Shall be returned when a new "Individual NS descriptor" resource
and the associated NS descriptor identifier has been created successfully.
The response body shall contain a representation of the created NS descriptor
resource, as defined in clause 5.5.2.2.
The HTTP response shall include a "Location" HTTP header that contains the
resource URI of the created NS descriptor resource.
schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfo"
headers:
......@@ -186,7 +184,9 @@ paths:
The VNFM shall support this parameter.
The following attributes shall be excluded from the NsdInfo structure in the response body if this
parameter is provided, or none of the parameters "all_fields," "fields", "exclude_fields", "exclude_default"
are provided: userDefinedData.
are provided:
- userDefinedData
- onboardingFailureDetails
- name: nextpage_opaque_marker
in: query
description: >
......@@ -207,7 +207,8 @@ paths:
description: >
200 OK
Information about zero or more NS descriptors.
Shall be returned when information about zero or
more NS descriptors has been queried successfully.
The response body shall contain in an array the
representations of zero or more NS descriptors, as
defined in clause 5.5.2.2.
......@@ -308,7 +309,8 @@ paths:
description: >
200 OK
Information about the individual NS descriptor.
Shall be returned when information about the individual
NS descriptor has been read successfully.
The response body shall contain a representation of
the individual NS descriptor, as defined in
clause 5.5.2.2.
......@@ -372,7 +374,8 @@ paths:
schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/NsdInfoModifications"
description: >
Parameters for the modification of an individual NS descriptor resource.
Parameters for the modification of an individual NS descriptor resource, as defined in clause 5.5.2.1.
The Content-Type header shall be set to "application/merge-patch+json" according to IETF RFC 7396.
- name: Content-Type
description: >
The MIME type of the body of the request.
......@@ -385,7 +388,7 @@ paths:
description: >
200 OK
The operation has been completed successfully.
Shall be returned when the operation has been accepted and completed successfully.
The response body shall contain attribute modifications for an 'Individual NS Descriptor'
resource (see clause 5.5.2.6).
headers:
......@@ -423,19 +426,19 @@ paths:
406:
$ref: "../responses/SOL005_resp.yaml#/responses/406"
409:
description: >
409 CONFLICT
Error: The operation cannot be executed currently,
due to a conflict with the state of the resource.
Typically, this is due to an operational state
mismatch, i.e. enable an already enabled or
disable an already disabled individual NS
descriptor resource, or the "nsdOnboardingState"
is not ONBOARDED.
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
# description: >
# 409 CONFLICT
#
# Error: The operation cannot be executed currently,
# due to a conflict with the state of the resource.
# Typically, this is due to an operational state
# mismatch, i.e. enable an already enabled or
# disable an already disabled individual NS
# descriptor resource, or the "nsdOnboardingState"
# is not ONBOARDED.
# The response body shall contain a ProblemDetails
# structure, in which the "detail" attribute shall convey
# more information about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/409"
412:
$ref: "../responses/SOL005_resp.yaml#/responses/412"
......@@ -472,7 +475,7 @@ paths:
description: >
204 NO CONTENT
The operation has completed successfully.
Shall be returned when the operation has completed successfully.
The response body shall be empty.
headers:
WWW-Authenticate:
......@@ -502,19 +505,19 @@ paths:
406:
$ref: "../responses/SOL005_resp.yaml#/responses/406"
409:
description: >
409 CONFLICT
Error: The operation cannot be executed currently,
due to a conflict with the state of the resource.
Typically, this is due to the fact the NS descriptor
resource is in the enabled operational state (i.e.
operationalState = ENABLED) or there are running
NS instances using the concerned individual NS
descriptor resource (i.e. usageState = IN_USE).
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
# description: >
# 409 CONFLICT
#
# Error: The operation cannot be executed currently,
# due to a conflict with the state of the resource.
# Typically, this is due to the fact the NS descriptor
# resource is in the enabled operational state (i.e.
# operationalState = ENABLED) or there are running
# NS instances using the concerned individual NS
# descriptor resource (i.e. usageState = IN_USE).
# The response body shall contain a ProblemDetails
# structure, in which the "detail" attribute shall convey
# more information about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/409"
500:
$ref: "../responses/SOL005_resp.yaml#/responses/500"
......@@ -524,7 +527,7 @@ paths:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
###############################################################################
# NSD Content #
# NSD Archive Content #
###############################################################################
'/ns_descriptors/{nsdInfoId}/nsd_content':
#ETSI GS NFV-SOL 005 V2.4.1 location: 5.4.4
......@@ -550,17 +553,20 @@ paths:
get:
summary: Fetch the content of a NSD.
description: >
The GET method fetches the content of the NSD.
The NSD can be implemented as a single file or as a collection of multiple files. If the NSD is implemented in the form
of multiple files, a ZIP file embedding these files shall be returned. If the NSD is implemented as a single file, either
that file or a ZIP file embedding that file shall be returned.
The selection of the format is controlled by the "Accept" HTTP header passed in the GET request:
• If the "Accept" header contains only "text/plain" and the NSD is implemented as a single file, the file shall be
returned; otherwise, an error message shall be returned.
• If the "Accept" header contains only "application/zip", the single file or the multiple files that make up the
NSD shall be returned embedded in a ZIP file.
• If the "Accept" header contains both "text/plain" and "application/zip", it is up to the NFVO to choose the
format to return for a single-file NSD; for a multi-file NSD, a ZIP file shall be returned.
The GET method fetches the content of the NSD archive.
The NSD archive is implemented as a single zip file.
The content of the NSD archive is provided as onboarded,
i.e. depending on the security option used, the CSAR wrapped
in a ZIP archive together with an external signature is returned,
as defined in clause 5.1 of ETSI GS NFV-SOL 007.
NOTE: Information about the applicable security option can be
obtained by evaluating the "archiveSecurityOption"
attribute in the "nsdInfo" structure.
This method shall follow the provisions specified in the T
ables 5.4.4.3.2-1 and 5.4.4.3.2-2 for URI query parameters,
request and response data structures, and response codes.
parameters:
- name: Accept
description: >
......@@ -576,27 +582,21 @@ paths:
required: false
type: string
description: >
"The request may contain a "Range" HTTP header to obtain single
range of bytes from the NSD file. This can be used to continue an aborted
transmission.If the NFVO does not support range requests, the NFVO
shall ignore the 'Range" header, process the GET request, and return
the whole NSD file with a 200 OK response (rather than returning a 4xx
error status code)."
The request may contain a "Range" HTTP header to obtain single
range of bytes from the NSD archive.
This can be used to continue an aborted transmission.
If the Range header is present in the request and the NFVO does
not support responding to range requests with a 206 response,
it shall return a 200 OK response instead as defined below.
responses:
200:
description: >
200 OK
Shall be returned when the content of the NSD has
been read successfully.
The payload body shall contain a copy of the file
representing the NSD or a ZIP file that contains the
file or multiple files representing the NSD, as
specified above.
The "Content-Type" HTTP header shall be set
according to the format of the returned file, i.e. to
"text/plain" for a YAML file or to "application/zip" for
a ZIP file.
Shall be returned when the content of the NSD has been read successfully.
The payload body shall contain a copy of the ZIP file that contains the NSD file structure.
The "Content-Type" HTTP header shall be set to "application/zip".
headers:
Content-Type:
description: The MIME type of the body of the response.
......@@ -618,18 +618,18 @@ paths:
maximum: 1
minimum: 1
206:
description: >
206 PARTIAL CONTENT
On success, if the NFVO supports range requests,
a single consecutive byte range from the content of
the NSD file is returned.
The response body shall contain the requested part
of the NSD file.
The "Content-Range" HTTP header shall be
provided according to IETF RFC 7233.
The "Content-Type" HTTP header shall be set as
defined above for the "200 OK" response.
# description: >
# 206 PARTIAL CONTENT
#
# On success, if the NFVO supports range requests,
# a single consecutive byte range from the content of
# the NSD file is returned.
# The response body shall contain the requested part
# of the NSD file.
# The "Content-Range" HTTP header shall be
# provided according to IETF RFC 7233.
# The "Content-Type" HTTP header shall be set as
# defined above for the "200 OK" response.
$ref: "../responses/SOL005_resp.yaml#/responses/206"
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
......@@ -642,40 +642,40 @@ paths:
405:
$ref: "../responses/SOL005_resp.yaml#/responses/405"
406:
description: >
406 NOT ACCEPTABLE
If the "Accept" header does not contain at least one
name of a content type for which the NFVO can
provide a representation of the NSD, the NFVO
shall respond with this response code.
The "ProblemDetails" structure may be included
with the "detail" attribute providing more information
about the error.
# description: >
# 406 NOT ACCEPTABLE
#
# If the "Accept" header does not contain at least one
# name of a content type for which the NFVO can
# provide a representation of the NSD, the NFVO
# shall respond with this response code.
# The "ProblemDetails" structure may be included
# with the "detail" attribute providing more information
# about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/406"
409:
description: >
409 CONFLICT
Shall be returned upon the following error: The
operation cannot be executed currently, due to a
conflict with the state of the resource.
Typically, this is due to the fact
"nsdOnboardingState" has a value different from
ONBOARDED.
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
# description: >
# 409 CONFLICT
#
# Shall be returned upon the following error: The
# operation cannot be executed currently, due to a
# conflict with the state of the resource.
# Typically, this is due to the fact
# "nsdOnboardingState" has a value different from
# ONBOARDED.
# The response body shall contain a ProblemDetails
# structure, in which the "detail" attribute shall convey
# more information about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/409"
416:
description: >
416 RANGE NOT SATISFIABLE
The byte range passed in the "Range" header did
not match any available byte range in the NSD file
(e.g. "access after end of file").
The response body may contain a ProblemDetails
structure.
# description: >
# 416 RANGE NOT SATISFIABLE
#
# The byte range passed in the "Range" header did
# not match any available byte range in the NSD file
# (e.g. "access after end of file").
# The response body may contain a ProblemDetails
# structure.
$ref: "../responses/SOL005_resp.yaml#/responses/416"
500:
$ref: "../responses/SOL005_resp.yaml#/responses/500"
......@@ -687,42 +687,33 @@ paths:
put:
summary: Upload the content of a NSD.
description: >
The PUT method is used to upload the content of a NSD.
The NSD to be uploaded can be implemented as a single file or as a collection of multiple files, as defined in
clause 5.4.4.3.2. If the NSD is implemented in the form of multiple files, a ZIP file embedding these files shall be
uploaded. If the NSD is implemented as a single file, either that file or a ZIP file embedding that file shall be uploaded.
ETSI
47 ETSI GS NFV-SOL 005 V2.6.1 (2019-04)
The "Content-Type" HTTP header in the PUT request shall be set accordingly based on the format selection of the
NSD:
• If the NSD to be uploaded is a text file, the "Content-Type" header is set to "text/plain".
• If the NSD to be uploaded is a zip file, the "Content-Type" header is set to "application/zip".
The PUT method is used to upload the content of an NSD archive.
The NSD to be uploaded is implemented as a single ZIP file as defined in clause 5.4.4.3.2.
The "Content-Type" HTTP header in the PUT request shall be set to "application/zip".
This method shall follow the provisions specified in the Tables 5.4.4.3.3-1 and
5.4.4.3.3-2 for URI query parameters, request and response data structures, and response codes.
parameters:
- name: Accept
- name: Content-Type
description: >
Content-Types that are acceptable for the response.
The payload body contains a copy of the file representing the NSD
or a ZIP file that contains the file or multiple files representing the NSD.
The payload body contains a ZIP file that represents the NSD archive, as specified above.
The request shall set the "Content-Type" HTTP header to "application/zip".
in: header
required: true
type: string
enum:
- text/plain
- application/zip
responses:
202:
description: >
202 ACCEPTED
The NSD content has been accepted for uploading,
but the processing has not been completed. It is
expected to take some time for processing
(asynchronous mode).
Shall be returned when the NSD archive has been accepted for uploading,
but the processing has not been completed. It is expected to take some
time for processing (asynchronous mode).
The response body shall be empty.
The client can track the uploading progress by
receiving the "NsdOnBoardingNotification" and
"NsdOnBoardingFailureNotification" from the NFVO
or by reading the status of the individual NS descriptor
The API consumer can track the uploading progress by receiving the
"NsdOnBoardingNotification" and "NsdOnBoardingFailureNotification"
from the NFVO or by reading the status of the individual NS descriptor
resource using the GET method.
headers:
Content-Type:
......@@ -779,17 +770,275 @@ paths:
406:
$ref: "../responses/SOL005_resp.yaml#/responses/406"
409:
# description: >
# 409 CONFLICT
#
# Error: The operation cannot be executed currently,
# due to a conflict with the state of the resource.
# Typically, this is due to the fact that the
# NsdOnboardingState has a value other than
# CREATED.
# The response body shall contain a ProblemDetails
# structure, in which the "detail" attribute shall convey
# more information about the error.
$ref: "../responses/SOL005_resp.yaml#/responses/409"
500:
$ref: "../responses/SOL005_resp.yaml#/responses/500"
503:
$ref: "../responses/SOL005_resp.yaml#/responses/503"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
###############################################################################
# NSD #
###############################################################################
'/ns_descriptors/{nsdInfoId}/nsd':
#ETSI GS NFV-SOL 005 V2.4.1 location: 5.4.4a
parameters:
- name: nsdInfoId
in: path
required: true
type: string
- name: Authorization
description: >
The authorization token for the request.
Reference: IETF RFC 7235.
in: header
required: false
type: string
- name: Version
description: >
Version of the API requested to use when responding to this request.
in: header
required: true
type: string
get:
description: >
The GET method reads the content of the NSD within an NSD archive.
The NSD can be implemented as a single file or as a collection of
multiple files. If the NSD is implemented in the form of multiple files,
a ZIP file embedding these files shall be returned. If the NSD is implemented
as a single file, either that file or a ZIP file embedding that file shall be returned.
The selection of the format is controlled by the "Accept" HTTP header passed in the GET request:
• If the "Accept" header contains only "text/plain" and the NSD is implemented as a single file,
the file shall be returned; otherwise, an error message shall be returned.
• If the "Accept" header contains only "application/zip", the single file or
the multiple files that make up the NSD shall be returned embedded in a ZIP file.
• If the "Accept" header contains both "text/plain" and "application/zip", it is up
to the NFVO to choose the format to return for a single-file NSD; for a multi-file NSD,
a ZIP file shall be returned.
The default format of the ZIP file shall be the one specified in ETSI GS NFV-SOL 007
where only the YAML files representing the NSD, and information necessary to navigate
the ZIP file and to identify the file that is the entry point for parsing the NSD and
(if requested) further security information are included. This means that the content
of the ZIP archive shall contain the following files from the NSD archive:
• TOSCA.meta (if available in the NSD archive);
• the main service template (either as referenced from TOSCA.meta or available as a
file with the extension ".yml" or ".yaml" from the root of the archive);
• every component of the NSD referenced (recursively) from the main service template;
• the related security information, if the "include_signatures" URI parameter is provided, as follows:
- the manifest file;
- the singleton certificate file in the root of the NSD archive (if available in the NSD archive);
- the signing certificates of the individual files included in the ZIP archive
(if available in the NSD archive);
- the signatures of the individual files (if available in the NSD archive).
This method shall follow the provisions specified in the Tables 5.4.4a.3.2-1 and 5.4.4a.3.2-2 for
URI query parameters, request and response data structures, and response codes.
parameters:
- name: include_signatures
in: query
required: false
type: string
description: >
If this parameter is provided, the NFVO shall include in the ZIP
file the security information as specified above.
This URI query parameter is a flag, i.e. it shall have no value.
The NFVO shall support this parameter.
- name: Accept
in: header
required: true
type: string
enum:
- text/plain
- application/zip
description: >
The request shall contain the appropriate entries in the "Accept"
HTTP header as defined above.
responses:
200:
description: >
200 OK
Shall be returned when the content of the NSD has been read successfully.
The payload body shall contain a copy of the file representing the NSD or
a ZIP file that contains the file or multiple files representing the NSD,
as specified above.
The "Content-Type" HTTP header shall be set according to the format of
the returned file. It shall be set to "text/plain" for a YAML file.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
type: string
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP request
has provided an invalid authorization token.
maximum: 1
minimum: 0
Version:
description: >
Version of the API used in the response.
type: string
maximum: 1
minimum: 1
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
401:
$ref: "../responses/SOL005_resp.yaml#/responses/401"
403:
$ref: "../responses/SOL005_resp.yaml#/responses/403"
404:
$ref: "../responses/SOL005_resp.yaml#/responses/404"
405:
$ref: "../responses/SOL005_resp.yaml#/responses/405"
406:
$ref: "../responses/SOL005_resp.yaml#/responses/406"
409:
$ref: "../responses/SOL005_resp.yaml#/responses/409"
500:
$ref: "../responses/SOL005_resp.yaml#/responses/500"
503:
$ref: "../responses/SOL005_resp.yaml#/responses/503"
504:
$ref: "../responses/SOL005_resp.yaml#/responses/504"
###############################################################################
# NSD Archive Manifest #
###############################################################################
'/ns_descriptors/{nsdInfoId}/manifest':
#ETSI GS NFV-SOL 005 V2.4.1 location: 5.4.4b
parameters:
- name: nsdInfoId
description: >
Identifier of the individual NS descriptor.
This identifier can be retrieved from the resource referenced by
the "Location" HTTP header in the response to a POST request creating
a new NS descriptor resource. It can also be retrieved from the "id"
attribute in the payload body of that response.
in: path
required: true
type: string
- name: Authorization
description: >
The authorization token for the request.
Reference: IETF RFC 7235.
in: header
required: false
type: string
- name: Version
description: >
Version of the API requested to use when responding to this request.
in: header
required: true
type: string
get:
summary: Fetch the content of the manifest in an NSD archive.
description: >
The GET method reads the content of the manifest file within an NSD archive.
This method shall follow the provisions specified in the Tables 5.4.4b.3.2-1
and 5.4.4b.3.2-2 for URI query parameters, request and response data structures,
and response codes.
parameters:
- name: Accept
description: >
Content-Types that are acceptable for the response.
in: header
required: true
type: string
enum:
- text/plain
- application/zip
- name: include_signatures
in: query
required: false
type: string
description: >
409 CONFLICT
If this parameter is provided, the NFVO shall return the manifest and
related security information (signature and certificate) either in a
single text file if the signature and certificate are included in the
manifest file, or in a zip file containing the manifest and the certificate
file, if this is provided as a separate file in the NSD archive.
If this parameter is not given, the NFVO shall provide only a copy of the
manifest file, as onboarded. If the security information is included in the
onboarded manifest, it shall also be included in the returned copy.
This URI query parameter is a flag, i.e. it shall have no value.
The NFVO shall support this parameter.
responses:
200:
description: >
200 OK
Error: The operation cannot be executed currently,
due to a conflict with the state of the resource.
Typically, this is due to the fact that the
NsdOnboardingState has a value other than
CREATED.
The response body shall contain a ProblemDetails
structure, in which the "detail" attribute shall convey
more information about the error.
Shall be returned when the content of the manifest file has been read successfully.
If the "include_signatures" URI query parameter was absent in the request, or if the
manifest file has all security-related information embedded (i.e. there is no separate
certificate file), the payload body shall contain a copy of the manifest file of the
NSD archive, and the "Content-Type" HTTP header shall be set to "text/plain".
If the "include_signatures" URI query parameter was present in the related request and
the manifest file does not have all the security-related information embedded (i.e. there
is a separate certificate file), the "Content-Type" HTTP header shall be set to "application/zip"
and the payload body shall contain a ZIP archive which includes:
- a copy of the manifest file of the NSD archive;
- a copy of the related individual certificate file.
headers:
Content-Type:
description: The MIME type of the body of the response.
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
type: string
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP request
has provided an invalid authorization token.
maximum: 1
minimum: 0
Version:
description: >
Version of the API used in the response.
type: string
maximum: 1
minimum: 1
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
401:
$ref: "../responses/SOL005_resp.yaml#/responses/401"
403:
$ref: "../responses/SOL005_resp.yaml#/responses/403"