Add error handling for maximum length of values
Bug #1406457 reported by
Adrian Otto
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Triaged
|
Wishlist
|
rajiv |
Bug Description
Add graceful error handling to politely decline to set a value, such as a pod label or image name that would cause the value to exceed the maximum configured length. Make the maximum configured length settable in the magnum configuration file. Allow different maximum lengths to be applied to different fields of each object. Use sensible defaults for these values that are known to work with a standard MySQL backing store.
Example of code needing this work applied:
https:/
Changed in magnum: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in magnum: | |
assignee: | nobody → Madhuri Kumari (madhuri-rai07) |
description: | updated |
Changed in magnum: | |
milestone: | none → mitaka-1 |
Changed in magnum: | |
assignee: | nobody → rajiv (rajiv-kumar) |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/179416 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=88fd313abd6 f391a0ed537221d e6b8f49f42ecd0
Committed: https:/
Submitter: Jenkins
Branch: master
commit 88fd313abd6f391 a0ed537221de6b8 f49f42ecd0
Author: Tom Cammann <email address hidden>
Date: Fri May 1 15:56:46 2015 +0100
Add string length validation to names in APIs
Add string length validation bays, bay models and containers.
Change-Id: I50f39e6416bda1 a64f8bd997a0bb4 c38ead63bfd
Partial-Bug: 1406457