Adding custom headers capability to REST client

For YANG PATCH requests to ODL to work, they need to have a Content-
type header of application/yang.patch+json and should not have Accept
as application/json

Current REST client inserts a default header to the requests with this
content:

  Content-Type: application/json
  Accept: application/json

The solution was to add the possibility of sending custom headers alon-
gside the other parameters.

Change-Id: I2cf0cd2ef7b87f4f5a246d427dffafe266cb33f7
Issue-ID: CCSDK-926
Signed-off-by: ottero <rodrigo.ottero@est.tech>

1 files changed, 12 insertions, 4 deletions

diff --git a/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Definitions/data_types.json b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Definitions/data_types.json
index 9f35eef88..e5aa763ba 100644
--- a/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Definitions/data_types.json
+++ b/components/model-catalog/blueprint-model/test-blueprint/capability_restconf/Definitions/data_types.json
@@ -3,13 +3,21 @@
     "dt-config-assign-properties" : {
       "description" : "Dynamic DataType definition for workflow(config-assign).",
       "version" : "1.0.0",
-      "properties" : { },
+      "properties" : {
+        "entity" : {
+          "type" : "json"
+        }
+      },
       "derived_from" : "tosca.datatypes.Dynamic"
     },
-    "dt-configure-properties" : {
-      "description" : "Dynamic DataType definition for workflow(configure).",
+    "dt-config-deploy-properties" : {
+      "description" : "Dynamic DataType definition for workflow(config-deploy).",
       "version" : "1.0.0",
-      "properties" : { },
+      "properties" : {
+        "entity" : {
+          "type" : "json"
+        }
+      },
       "derived_from" : "tosca.datatypes.Dynamic"
     }
   }