JSON Schema Validation for query param
This is continuation of below BP-
https:/
In Ocata BP, query param validation framework was implemented with keypair API as example. Basically methods accept query param can be decorated with json schema to have consistency and to avoid DB failure for wrong param.
Blueprint information
- Status:
- Complete
- Approver:
- Matt Riedemann
- Priority:
- Low
- Drafter:
- Ghanshyam Mann
- Direction:
- Approved
- Assignee:
- Ghanshyam Mann
- Definition:
- Approved
- Series goal:
- Accepted for queens
- Implementation:
-
Implemented
- Milestone target:
-
queens-2
- Started by
- Ghanshyam Mann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
I'm OK with this as a specless blueprint provided it does not mean we have any microversion changes as a result. -- mriedem 20170905
Yea, it would not change any behavior and so does not need version bump. We discussed the 'limit' as int in quotes (as string) which is not valid case for query param
- http://
- test patches https:/
Gerrit topic: https:/
Addressed by: https:/
check query param for used_limits function
Addressed by: https:/
check query param for service's index function
Addressed by: https:/
check query param for server groups function
Addressed by: https:/
Implement query param schema for GET hypervisor(2.33)
Addressed by: https:/
Implement query param schema for simple_tenant_usage
Addressed by: https:/
Implement query param schema for delete assisted vol
Addressed by: https:/
Implement query param schema for host index
Addressed by: https:/
Implement query param schema for fping index
Addressed by: https:/
Implement query param schema for flavor index
Addressed by: https:/
Implement query param schema for migration index
Addressed by: https:/
Implement query param schema for quota set APIs
Addressed by: https:/
Implement query param schema for sec group APIs
Addressed by: https:/
Implement query param schema for volume, snapshot API
