schemas PMJobModifications and ThresholdModification added

SOL002/VNFPerformanceManagement-API/IndividualPmJob.robot

@@ -99,7 +99,7 @@ PATCH Individual VNF Performance Job
     ...    Post-Conditions: 
     Send Patch request for individual VNF Performance Job
     Check HTTP Response Status Code Is    200
-    Check HTTP Response Body Json Schema Is    PMJobModification
+    Check HTTP Response Body Json Schema Is    PMJobModifications
     
 PATCH Individual VNF Performance Job - Precondition failed
     [Documentation]    Test ID: 6.3.3.2.8

SOL002/VNFPerformanceManagement-API/IndividualThreshold.robot

@@ -95,7 +95,7 @@ PATCH Individual Threshold
     ...    Post-Conditions: The VNF Performance Threshold is not modified by the operation
     Send Patch request for individual VNF Performance Threshold
     Check HTTP Response Status Code Is    200
-    Check HTTP Response Body Json Schema Is    ThresholdModification
+    Check HTTP Response Body Json Schema Is    ThresholdModifications
     
     
 PATCH Individual Threshold - Precondition failed

SOL002/VNFPerformanceManagement-API/schemas/PMJobModifications.json

+ {
+    "description": "This type represents modifications to a PM job. It shall comply with the provisions defined in table 6.5.2.12-1.\n",
+    "type": "object",
+    "properties": {
+      "callbackUri": {
+        "description": "String formatted according to IETF RFC 3986.\n",
+        "type": "string"
+      },
+      "authentication": {
+        "type": "object",
+        "required": [
+          "authType"
+        ],
+        "properties": {
+          "authType": {
+            "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n  HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n  notification endpoint, use an OAuth 2.0 Bearer token, obtained\n  using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n  over a mutually authenticated TLS session, i.e. not only the\n  server is authenticated, but also the client is authenticated\n  during the TLS tunnel setup.\n",
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "BASIC",
+                "OAUTH2_CLIENT_CREDENTIALS",
+                "TLS_CERT"
+              ]
+            }
+          },
+          "paramsBasic": {
+            "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+            "type": "object",
+            "properties": {
+              "userName": {
+                "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+                "type": "string"
+              },
+              "password": {
+                "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+                "type": "string"
+              }
+            }
+          },
+          "paramsOauth2ClientCredentials": {
+            "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+            "type": "object",
+            "properties": {
+              "clientId": {
+                "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type.  Shall be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\n",
+                "type": "string"
+              },
+              "clientPassword": {
+                "description": "Client password to be used in the access token request of the OAuth 2.0 client credentials grant type.  Shall be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\n",
+                "type": "string"
+              },
+              "tokenEndpoint": {
+                "description": "String formatted according to IETF RFC 3986.\n",
+                "type": "string"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
\ No newline at end of file

SOL002/VNFPerformanceManagement-API/schemas/ThresholdModifications.json

+ {
+    "description": "This type represents modifications to a threshold. It shall comply with the provisions defined in table 6.5.2.11-1.\n",
+    "type": "object",
+    "properties": {
+      "callbackUri": {
+        "description": "String formatted according to IETF RFC 3986.\n",
+        "type": "string"
+      },
+      "authentication": {
+        "type": "object",
+        "required": [
+          "authType"
+        ],
+        "properties": {
+          "authType": {
+            "description": "Defines the types of Authentication / Authorization which the API consumer is willing to accept when receiving a notification. Permitted values: * BASIC: In every HTTP request to the notification endpoint, use\n  HTTP Basic authentication with the client credentials. \n* OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the\n  notification endpoint, use an OAuth 2.0 Bearer token, obtained\n  using the client credentials grant type.\n* TLS_CERT: Every HTTP request to the notification endpoint is sent\n  over a mutually authenticated TLS session, i.e. not only the\n  server is authenticated, but also the client is authenticated\n  during the TLS tunnel setup.\n",
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "BASIC",
+                "OAUTH2_CLIENT_CREDENTIALS",
+                "TLS_CERT"
+              ]
+            }
+          },
+          "paramsBasic": {
+            "description": "Parameters for authentication/authorization using BASIC. Shall be present if authType is \"BASIC\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+            "type": "object",
+            "properties": {
+              "userName": {
+                "description": "Username to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+                "type": "string"
+              },
+              "password": {
+                "description": "Password to be used in HTTP Basic authentication. Shall be present if it has not been provisioned out of band.\n",
+                "type": "string"
+              }
+            }
+          },
+          "paramsOauth2ClientCredentials": {
+            "description": "Parameters for authentication/authorization using OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is \"OAUTH2_CLIENT_CREDENTIALS\" and the contained information has not been provisioned out of band. Shall be absent otherwise.\n",
+            "type": "object",
+            "properties": {
+              "clientId": {
+                "description": "Client identifier to be used in the access token request of the OAuth 2.0 client credentials grant type.  Shall be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\n",
+                "type": "string"
+              },
+              "clientPassword": {
+                "description": "Client password to be used in the access token request of the OAuth 2.0 client credentials grant type.  Shall be present if it has not been provisioned out of band. The clientId and clientPassword passed in a subscription shall not be the same as the clientId and clientPassword that are used to obtain authorization for API requests. Client credentials may differ between subscriptions. The value of clientPassword should be generated by a random process.\n",
+                "type": "string"
+              },
+              "tokenEndpoint": {
+                "description": "String formatted according to IETF RFC 3986.\n",
+                "type": "string"
+              }
+            }
+          }
+        }
+      }
+    }
+  }
\ No newline at end of file