VNFPackageManagement.yaml 95.5 KB
Newer Older
        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.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          style: simple
          explode: false
          required: true
          schema:
            type: string
            enum:
              - text/plain
              - application/zip
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    VnfdInIndividualOnboardedVnfPackage.Get.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 that "onboardingState"
        of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    ManifestInIndividualVnfPackage.Get.200:
      description: |
        200 OK

        Shall be returned when the content of the manifest 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 VNF package 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 VNF package;
        •	a copy of the related individual certificate file.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          style: simple
          explode: false
          required: true
          schema:
            type: string
            enum:
              - text/plain
              - application/zip
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    ManifestInIndividualVnfPackage.Get.406:
      description: |
        406 Not Acceptable

        If the related request contained an "Accept" header
        not compatible with the Content type "application/zip"
        but the "include_signatures" flag was provided, the
        NFVO shall respond with this response code.
        The "ProblemDetails" structure may be included with
        the "detail" attribute providing more information about
        the error.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string

    ManifestInIndividualVnfPackage.Get.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 that "onboardingState"
        of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    ManifestInIndividualOnboardedVnfPackage.Get.200:
      description: |
        200 OK

        Shall be returned when the content of the manifest 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 VNF package 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 VNF package;
        •	a copy of the related individual certificate file.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          style: simple
          explode: false
          required: true
          schema:
            type: string
            enum:
              - text/plain
              - application/zip
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    ManifestInIndividualOnboardedVnfPackage.Get.406:
      description: |
        406 Not Acceptable

        If the related request contained an "Accept" header
        not compatible with the Content type "application/zip"
        but the "include_signatures" flag was provided, the
        NFVO shall respond with this response code.
        The "ProblemDetails" structure may be included with
        the "detail" attribute providing more information about
        the error.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string

    ManifestInIndividualOnboardedVnfPackage.Get.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 that "onboardingState"
        of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    IndividualVnfPackageContent.Get.200:
      description: |
        200 OK

        Shall be returned when the whole content of the VNF package file has been read successfully.
        The response body shall include a copy of the VNF package file.
        The "Content-Type HTTP" header shall be set according to the type of the file,
        i.e. to "application/zip" for a VNF Package as defined in ETSI GS  NFV SOL  004.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualVnfPackageContent.Get.206:
      description: |
        206 PARTIAL CONTENT

        If the NFVO supports range requests, this response shall be returned when
        a single consecutive byte range from the content of the VNF package file
        has been read successfully according to the request.
        The response body shall contain the requested part of the VNF package 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.
      headers:
        Content-Range:
          required : true
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: The MIME type of the body of the response.
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualVnfPackageContent.Get.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 that
        "onboardingState" of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    IndividualVnfPackageContent.Get.416:
      description: |
        416 Range Not Satisfiable

        Shall be returned upon the following error: The byte
        range passed in the "Range" header did not match
        any available byte range in the VNF package file
        (e.g. "access after end of file").
        The response body may contain a ProblemDetails
        structure
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualOnboardedVnfPackageContent.Get.200:
      description: |
        200 OK

        Shall be returned when the whole content of the VNF package file has been read successfully.
        The response body shall include a copy of the VNF package file.
        The "Content-Type HTTP" header shall be set according to the type of the file,
        i.e. to "application/zip" for a VNF Package as defined in ETSI GS  NFV SOL  004.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualOnboardedVnfPackageContent.Get.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 that
        "onboardingState" of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    IndividualOnboardedVnfPackageContent.Get.416:
      description: |
        416 Range Not Satisfiable

        Shall be returned upon the following error: The byte
        range passed in the "Range" header did not match
        any available byte range in the VNF package file
        (e.g. "access after end of file").
        The response body may contain a ProblemDetails
        structure
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string

    IndividualVnfPackageArtifact.Get.200:
      description: |
        200 OK

        Shall be returned when the whole content of the artifact file has
        been read successfully.

        If the "include_signatures" request URI parameter was not provided in
        the related request, the payload body shall contain a copy of the artifact
        file from the VNF package, as defined by ETSI GS NFV-SOL 004 and the "Content-Type"
        HTTP header shall be set according to the content type of the artifact file.
        If the artifact is encrypted, the header shall be set to the value "application/cms"
        (IETF RFC 7193). If the content type cannot be determined, the header shall be set
        to the value "application/octet-stream".

        If the "include_signatures" request URI parameter was provided in the related request,
        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 artifact file from the VNF package, as defined by ETSI GS NFV SOL 004;
        •	the related security information (individual signature file and optional related
            individual certificate file).
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the response.
            The "Content-Type" HTTP header shall be set according to the
            content type of the artifact file. If the content type cannot
            be determined, the header shall be set to the value
            "application/octet-stream".
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualVnfPackageArtifact.Get.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 that
        "onboardingState" of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    IndividualVnfPackageArtifact.Get.416:
      description: |
        416 Range Not Satisfiable

        Shall be returned upon the following error: The byte
        range passed in the "Range" header did not match
        any available byte range in the artifact file
        (e.g. "access after end of file").
        The response body may contain a ProblemDetails
        structure
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualOnboardedVnfPackageArtifact.Get.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 that
        "onboardingState" of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    IndividualOnboardedVnfPackageArtifact.Get.416:
      description: |
        416 Range Not Satisfiable

        Shall be returned upon the following error: The byte
        range passed in the "Range" header did not match
        any available byte range in the artifact file
        (e.g. "access after end of file").
        The response body may contain a ProblemDetails
        structure
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualVnfPackageArtifacts.Get.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 that
        "onboardingState" of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    IndividualVnfPackageArtifacts.Get.416:
      description: |
        416 Range Not Satisfiable

        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 that
        "onboardingState" of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualOnboardedVnfPackageArtifacts.Get.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 that
        "onboardingState" of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: |
            The MIME type of the body of the response. Reference: IETF RFC 7231
          style: simple
          explode: false
          schema:
            type: string
      content:
        application/json:
          schema:
            $ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"

    IndividualOnboardedVnfPackageArtifacts.Get.416:
      description: |
        416 Range Not Satisfiable

        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 that
        "onboardingState" of the VNF package 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.
      headers:
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualOnboardedVnfPackageContent.Get.206:
      description: |
        206 PARTIAL CONTENT

        If the NFVO supports range requests, this response shall be returned when
        a single consecutive byte range from the content of the VNF package file
        has been read successfully according to the request.
        The response body shall contain the requested part of the VNF package 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.
      headers:
        Content-Range:
          required : true
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: The MIME type of the body of the response.
          style: simple
          explode: false
          required: true
          schema:
            type: string
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualVnfPackageArtifacts.Get.200:
      description: |
        200 OK

        Shall be returned when the whole content of the archive containing
        the artifact files has been read successfully.
        The payload body shall be a ZIP archive containing the requested
        set of artifacts selected according to the provisions specified above
        in this clause, and, if the flag "include_signatures" was provided in
        the related request, the applicable signature files and, if available,
        the separate certificate files from the VNF package.
        The "Content-Type" HTTP header shall be set to "application/zip".
      headers:
        Content-Type:
          description: |
            The MIME type of the body of the response.
            The "Content-Type" HTTP header shall be set according to the
            content type of the artifact file. If the content type cannot
            be determined, the header shall be set to the value
            "application/octet-stream".
          style: simple
          explode: false
          schema:
            type: string
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualVnfPackageArtifact.Get.206:
      description: |
        206 PARTIAL CONTENT

        If the NFVO supports range requests and the "include_signatures" request
        URI parameter was not present in the related request, this response shall
        be returned when a single consecutive byte range from the content of the
        artifact file, if the NFVO supports range requests has been read successfully
        according to the request.
        The response body shall contain the requested part of the VNF
        package 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.
      headers:
        Content-Range:
          required : true
          style: simple
          explode: false
          schema:
            type: string
        Content-Type:
          description: The MIME type of the body of the response.
          style: simple
          explode: false
          required: true
          schema:
            type: string
        WWW-Authenticate:
          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.
          style: simple
          explode: false
          schema:
            type: string
        Version:
          description: The used API version.
          style: simple
          explode: false
          schema:
            type: string

    IndividualVnfPackageArtifacts.Get.206:
      description: |
        206 PARTIAL CONTENT

        If the NFVO supports range requests, this response shall be returned
        when a single consecutive byte range from the content of the archive
        that would have been returned in a "200 OK" response has been read
        successfully according to the request.
        The response body shall contain the requested part of the archive.
        The "Content-Type" HTTP header shall be set to "application/zip".
        The "Content-Range" HTTP header shall be provided according to IETF RFC 7233.
      headers:
        Content-Range:
          required : true
          style: simple
          explode: false
          schema: