Zun

Input to APIs should be validated

Registered by Pradeep Kumar Singh

Currently type validation and whether parameter is mandatory or not is done through some Types implemenetd in zun.
I think when we have large number of types and other permutation combination of the parameter, its going to be difficult.
So we should find a way for this, like using Jsonschema or something else.
https://bugs.launchpad.net/zun/+bug/1612103
https://bugs.launchpad.net/zun/+bug/1634780

Blueprint information

Status:
Complete
Approver:
hongbin
Priority:
Medium
Drafter:
Pradeep Kumar Singh
Direction:
Approved
Assignee:
Pradeep Kumar Singh
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Pradeep Kumar Singh
Completed by
Pradeep Kumar Singh

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/api-json-input-validation,n,z

Addressed by: https://review.openstack.org/409503
    Propose api-validation blueprint

Addressed by: https://review.openstack.org/411125
    Initial implementation of jsonschema validatior

Addressed by: https://review.openstack.org/413676
    Add validators to the controllers

Gerrit topic: https://review.openstack.org/#q,topic:api-json-input-validation,n,z

Addressed by: https://review.openstack.org/417658
    [WIP][NOT_FOR_REVIEW] Remove the Container class

Addressed by: https://review.openstack.org/420503
    Remove Image and ZunService class from controllers

Addressed by: https://review.openstack.org/420605
    Add support for validation of query parameters

Addressed by: https://review.openstack.org/423624
    Remove Link class

@Pradeep, it looks this BP is already implemented?
-- hongbin 2017-03-05

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.