Resource primary key should not be a UUID
Bug #1415237 reported by
Zane Bitter
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Angus Salkeld |
Bug Description
We switched most database tables over to having auto-incrementing integers as primary keys. These are used for all references between tables in the database, while UUIDs are used for user-facing identification of objects. However the Resource table still uses a UUID as a primary key. We want to switch this to an auto-incrementing integer, while leaving the UUID column in place (it is used e.g. to generate physical resource names).
Changed in heat: | |
milestone: | kilo-2 → kilo-3 |
Changed in heat: | |
assignee: | Angus Salkeld (asalkeld) → Oleksii Chuprykov (ochuprykov) |
Changed in heat: | |
assignee: | Oleksii Chuprykov (ochuprykov) → Angus Salkeld (asalkeld) |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/159741
Review: https:/