Inconsistent naming of API Server response keys

[danielfurman]

Current behaviour

Server returns data in following JSON (example for Show operation):

return c.JSON(http.StatusOK, map[string]interface{}{
    "virtual_network": result,
})

Current Server response keys:

• “virtual-network” key in Server response for create, update
• “virtual-networks” key in Server response for list operation
• “virtual_network” key in Server response for show operation

It requires CLI code to do some string replacements, which shouldn't be needed.

Proposed solution

I think it would be the best to use following:

• Schema.ID for create, update, show operation (f.e. "virtual_network")
• Schema.Plural for list operation (f.e. "virtual_networks")

Another option are:

• use "data" response key for all resources
• use result object (naming from code snippet) as JSON root (no place for future metadata next to resource data in this option)