From 3ac0d20b08dd8c31ff85ad3ca5c53df11b6d96e4 Mon Sep 17 00:00:00 2001
From: ottero <rodrigo.ottero@est.tech>
Date: Sun, 17 Mar 2019 19:38:32 +0000
Subject: 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>
---
.../resource-dictionary/starter-dictionary/pnf-name.json | 15 +++++++++++++++
1 file changed, 15 insertions(+)
create mode 100755 components/model-catalog/resource-dictionary/starter-dictionary/pnf-name.json
(limited to 'components/model-catalog/resource-dictionary/starter-dictionary/pnf-name.json')
diff --git a/components/model-catalog/resource-dictionary/starter-dictionary/pnf-name.json b/components/model-catalog/resource-dictionary/starter-dictionary/pnf-name.json
new file mode 100755
index 000000000..edcc3e9a0
--- /dev/null
+++ b/components/model-catalog/resource-dictionary/starter-dictionary/pnf-name.json
@@ -0,0 +1,15 @@
+{
+ "name" : "pnf-name",
+ "tags" : "pnf-name",
+ "updated-by" : "Rodrigo Ottero <rodrigo.ottero@est.tech>",
+ "property" : {
+ "description" : "pnf-name",
+ "type" : "string"
+ },
+ "sources" : {
+ "input" : {
+ "type" : "source-input",
+ "properties" : { }
+ }
+ }
+}
\ No newline at end of file
--
cgit