update SOL002VNFIndicator

src/SOL002/VNFIndicator/VNFIndicator.yaml

@@ -211,7 +211,7 @@ paths:
         "416":
           $ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/416
         "422":
-          $ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/422
+          $ref: '#/components/responses/VnfIndicatorSubscription.Post.422'
         "429":
           $ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/429
         "500":
@@ -365,9 +365,9 @@ components:
       in: path
       description: |
         Identifier of this subscription. NOTE:
-         This identifier can be retrieved from the resource referenced by the "Location" HTTP header
-         in the response to a POST request creating a new subscription resource. It can also be retrieved
-         from the "id" attribute in the payload body of that response.
+        This identifier can be retrieved from the resource referenced by the "Location" HTTP header
+        in the response to a POST request creating a new subscription resource. It can also be retrieved
+        from the "id" attribute in the payload body of that response.
       required: true
       style: simple
       explode: false
@@ -562,6 +562,45 @@ components:
             items:
               $ref: ../../definitions/SOL002SOL003VNFIndicator_def.yaml#/definitions/VnfIndicatorSubscription
 
+    VnfIndicatorSubscription.Post.422:
+      description: |
+        422 Unprocessable Content
+
+        Shall be returned upon the following error: The content type of the message content is supported and 
+        the message content of a request contains syntactically correct data but the data cannot be processed.
+        The general cause for this error and its handling is specified in clause 6.4 of ETSI GS NFV-SOL 013 [6], 
+        including rules for the presence of the response body.
+        Specifically in case of this resource, the response code 422 shall also be returned if the VNFM has tested 
+        the Notification endpoint as described in clause 8.4.7.3.2 and the test has failed.
+        In this case, the "detail" attribute in the "ProblemDetails" structure 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: Version of the API used in the response.
+          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"
+
     VnfIndicatorSubscription.Get.200:
       description: |
         200 OK