Service template validation in ServiceChainNode with heat
Bug #1387462 reported by
Hemanth Ravi
This bug report is a duplicate of:
Bug #1418839: Service config in yaml cannot be loaded.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Confirmed
|
Medium
|
Magesh GV | ||
Bug Description
Currently template validation is done via json.loads(). This doesn't work for templates in yaml as well as valid json files but invalid heat syntax. Use the API equivalent for the following to validate:
heat template-validate --template-file <filename>
| Changed in group-based-policy: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Magesh GV (magesh-gv) |
| Changed in group-based-policy: | |
| milestone: | none → juno-release |
| status: | New → Confirmed |
Revision history for this message
| Magesh GV (magesh-gv) wrote | #1 |
| Changed in group-based-policy: | |
| milestone: | juno-release → kilo-gbp-1 |
| Changed in group-based-policy: | |
| milestone: | kilo-gbp-1 → kilo-gbp-2 |
Revision history for this message
| Magesh GV (magesh-gv) wrote | #2 |
To post a comment you must log in.
This is done in the gbp client today. The gbp client uses heatclient to convert the template file to json string.
Should this be moved to the server instead or should we verify if the current client also works with yaml templates.