Fix data handling for vnfd, config and param yaml templates
Bug #1591361 reported by
Sripriya
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Fix Released
|
Medium
|
Sridhar Ramaswamy |
Bug Description
Refactor the vnfd and vnf api to handle vnfd template, config and param files as json payloads instead of punting it under the generic 'attributes' attribute in VNF/VNFD API.
This will have an impact on DB as well.
Changed in tacker: | |
assignee: | nobody → Sripriya (sseetha) |
summary: |
- Fix data handling for vnfd and config yaml templates + Fix data handling for vnfd, config and param yaml templates |
description: | updated |
Changed in tacker: | |
importance: | Undecided → Low |
Changed in tacker: | |
assignee: | nobody → Janki Chhatbar (jankihchhatbar) |
Changed in tacker: | |
assignee: | Janki Chhatbar (jankihchhatbar) → Sripriya (sseetha) |
To post a comment you must log in.
I'd suggest we add "json" payload in addition to "string" version, deprecate "string" version in Newton and remove it in Ocata.