Plan API should return json/yaml as accept header specifies
Bug #1331093 reported by
Noorul Islam K M
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Solum |
Fix Released
|
Critical
|
Pierre Padrixe (stannie) |
Bug Description
This [1] patch actually changed the behavior of plan related APIs to return YAML instead of JSON.
Here [2] is the conversation on IRC in which we agreed that it should be JSON by default.
[1] https:/
[2] https:/
Changed in solum: | |
status: | New → Triaged |
importance: | Undecided → Critical |
assignee: | nobody → Pierre Padrixe (stannie) (pierre-padrixe) |
milestone: | none → juno-2 |
tags: | added: plan-improvements-versionning-and-yaml-support |
Changed in solum: | |
status: | Triaged → In Progress |
Changed in solum: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
I don't agree with the title of this bug: "API should always return json" is not appropriated IMO.
If you POST a Plan in YAML format you should be able to GET your template in YAML format.
And that's really weird to POST a Plan in YAML and then get a JSON in the response body of the post.
Specifying the format (YAML or JSON) in Accept-Type header and return the appropriate format in response would be a more appropriate solution