db column uuid validation is missing

[Kanagaraj Manickam]

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

[Angus Salkeld (asalkeld)]

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?

[Kanagaraj Manickam (kanagaraj-manickam)]

in all models where the id is treated as uuid, default values are set with uuid.uuid4(), but other places, which are not like engine_id used in Resource and other models, those are the places where forgien key constrains are not defined, Stack_id in SYncPoint is another example.

Even in model ids, there is no validation done on the value being stored, so programmatic ally if developer stores non-uuid format with 36 lenght string, still, model will allow to store it. and will lead to defective scenario.

as part of this defect all the models column who type is of UUID should be updated and test cases to be take care accordingly, I believe.

Intention is to make sure the uuid columns are in UUID format irrespective of whether its id column, foreign-key column or some other loosely coupled column, as mentioned above.

[Angus Salkeld (asalkeld)]

@kanagaraj-manickam it seems low value to me (in comparison to the other things we need to do).