Improve validation for memory field in container POST APIs
Bug #1611743 reported by
Madhuri Kumari
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zun |
Fix Committed
|
High
|
bharaththiruveedula | ||
Bug Description
Currently the type of field is string which is wrong, we should modify validation to check cases like:
* it should not be only string
* it should not be non-negative no.
* it should be more than 4MB.
etc.
| Changed in zun: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in zun: | |
| assignee: | nobody → bharaththiruveedula (bharath-ves) |
Revision history for this message
| bharaththiruveedula (bharath-ves) wrote | #1 |
| Changed in zun: | |
| status: | Confirmed → In Progress |
| Changed in zun: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Pushed the changes to https:/