db column uuid validation is missing
Bug #1439022 reported by
Kanagaraj Manickam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Low
|
Kanagaraj Manickam |
Bug Description
In heat, some of the columns in different tables are using the UUID as the format of the column, but there is no validation exist for these column's value.
So this bug is filed to add new sql alchemy type called UUID and use it in all the places, where those columns are made to hold uuid values
Changed in heat: | |
assignee: | nobody → Kanagaraj Manickam (kanagaraj-manickam) |
Changed in heat: | |
importance: | Undecided → Low |
Changed in heat: | |
status: | New → Triaged |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.
I really don't think we need to validate the uuid, when this is only added by str(uuid.uuid4()).
It's not like it's user inserted.
Why do we need this?