[RFE] introduce explicit database constraint naming conventions
Bug #1660365 reported by
milan k
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic Inspector |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
Based on the discussion in the multi-attribute node look-up patch[1]
We didn't explicitly name database constraints before.
This leads to issues if we want to modify/drop constraints in a future schema update[2]
[1] https:/
[2] http://
Changed in ironic-inspector: | |
importance: | Undecided → Wishlist |
tags: | added: rfe |
Changed in ironic-inspector: | |
status: | New → Triaged |
To post a comment you must log in.
Moving to wontfix. Ironic-inspector functionality is being merged into ironic, and as such we're not doing new feature development in ironic-inspector.