Fix issue #29 for Release 3 drop 7 (b1448064) · Commits · NFV - Network Functions Virtualisation / SOL002-SOL003

src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml

+178 −8

Original line number	Diff line number	Diff line
		@@ -200,8 +200,7 @@ paths:
		"406":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/406
		"412":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/412

		$ref: '#/components/responses/IndividualVnfInstance.Patch.412'
		"422":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/422
		"429":
		@@ -274,12 +273,11 @@ paths:
		"403":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/403
		"404":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/404
		$ref: '#/components/responses/ScaleVnfInstance.Post.404'
		"405":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/405
		"406":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/406

		"422":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/422
		"429":
		@@ -431,12 +429,11 @@ paths:
		"403":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/403
		"404":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/404
		$ref: '#/components/responses/HealVnfInstance.Post.404'
		"405":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/405
		"406":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/406

		"422":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/422
		"429":
		@@ -850,7 +847,7 @@ paths:
		"201":
		$ref: '#/components/responses/Subscriptions.Post.201'
		"303":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/303
		$ref: '#/components/responses/Subscriptions.Post.303'
		"400":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/400
		"401":
		@@ -863,7 +860,6 @@ paths:
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/405
		"406":
		$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/406

		"422":
		$ref: '#/components/responses/Subscriptions.Post.442'
		"429":
		@@ -1781,6 +1777,43 @@ components:
		schema:
		$ref: "../General_Definitions/SOL002_def.yaml#/definitions/ProblemDetails"

		IndividualVnfInstance.Patch.412:
		description: \|
		412 Precondition Failed

		Shall be returned upon the following error: A
		precondition given in an HTTP request header is
		not fulfilled.
		Typically, this is due to an ETag mismatch,
		indicating that the resource was modified by
		another entity.
		The response body should contain a
		ProblemDetails structure, in which the "detail"
		attribute should 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

		InstantiateVnfInstance.Post.202:
		description: \|
		202 ACCEPTED
		@@ -1900,6 +1933,53 @@ components:
		format: url
		content: {}

		ScaleVnfInstance.Post.404:
		description: \|
		404 NOT FOUND

		Shall be returned upon the following error: The API
		producer did not find a current representation for the
		target resource or is not willing to disclose that one
		exists.
		The general cause for this error and its handling is
		specified in clause 6.4 of ETSI GS NFV-SOL 013,
		including rules for the presence of the response body.
		Specifically in case of this task resource, the
		response code 404 shall also be returned if the task
		is not supported for the VNF instance represented by
		the parent resource, which means that the task
		resource consequently does not exist.
		In this case, the response body shall be present, and
		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: "../General_Definitions/SOL002_def.yaml#/definitions/ProblemDetails"

		ScaleVnfInstance.Post.409:
		description: \|
		409 CONFLICT
		@@ -2229,6 +2309,53 @@ components:
		format: url
		content: {}

		HealVnfInstance.Post.404:
		description: \|
		404 NOT FOUND

		Shall be returned upon the following error: The API
		producer did not find a current representation for the
		target resource or is not willing to disclose that one
		exists.
		The general cause for this error and its handling is
		specified in clause 6.4 of ETSI GS NFV-SOL 013,
		including rules for the presence of the response body.
		Specifically in case of this task resource, the
		response code 404 shall also be returned if the task
		is not supported for the VNF instance represented by
		the parent resource, which means that the task
		resource consequently does not exist.
		In this case, the response body shall be present, and
		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: "../General_Definitions/SOL002_def.yaml#/definitions/ProblemDetails"

		HealVnfInstance.Post.409:
		description: \|
		409 CONFLICT
		@@ -2931,6 +3058,49 @@ components:
		schema:
		$ref: "definitions/SOL002VNFLifecycleManagement_def.yaml#/definitions/LccnSubscription"

		Subscriptions.Post.303:
		description: \|
		303 See Other

		Shall be returned if a subscription with the same
		callback URI and the same filter already exists
		and the policy of the VNFM is to not create
		redundant subscriptions.
		The HTTP response shall include a "Location"
		HTTP header that contains the resource URI of
		the existing "Individual subscription" resource.
		The response body shall be empty.
		headers:
		Location:
		description: \|
		The resource URI of the created subscription resource.
		style: simple
		explode: false
		schema:
		type: string
		format: url
		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

		Subscriptions.Post.442:
		description: \|
		422 Unprocessable Content